ORA-01017: invalid username/password in TOAD, while connection with SQLPLUS is ok.

Problem: ORA-01017: invalid username/password in TOAD, while connection with SQLPLUS is ok.

Cause: TOAD Converts all the password to UPPERCASE

Solution: Users imported from a 10g database have a PASSWORD_VERSIONS value of "10G" and maintain case insensitive passwords independent of the SEC_CASE_SENSITIVE_LOGON parameter setting. Their passwords become case sensitive as soon as they are changed, assuming the SEC_CASE_SENSITIVE_LOGON parameter is set to TRUE.

The ignorecase parameter of the orapwd utility allows control over case sensitivity of passwords in the password file. The default value is "n", meaning the passwords are case sensitive. When privileged users (SYSDBA & SYSOPER) are imported from a previous release their passwords are included in the password file. These users will retain case insensitive passwords until the password is modified.

To create case insensitive passwords in the password file, recreate the password file using the ingnorecase=y option.

$ orapwd file=orapwDB11Gb entries=100 ignorecase=y password=mypassword

The passwords associated with database links are also case sensitive, which presents some issues when connecting between different releases:

• 11g to 11g: The database link must be created with the password in the correct case to match the remote users password.
• 11g to Pre-11g: The database link can be created with the password in any case as case is ignored by the remote database.
• Pre-11g to 11g: The remote user must have its password modified to be totally in upper case, as this is how it will be stored and passed by the Pre-11g database.

On making Oracle start a batch file (.bat) on Windows

 With Oracle 10g and dbms_scheduler it is possible to start a shell script (Unix) or a batch file (Windows). The following article tries to show how to do that for Windows.

More specifically, the batch file will delete the alert_log.html. Here's its content:

c:\ora_utils\del_alert.bat

del D:\oracle\databases\ora10\bdump\alert_ora10.log

ORA-12560 Error When Trying to Create New Database After New Install [ID 973264.1]

Applies to:

Oracle Server - Enterprise Edition - Version: 10.2.0.4.0 - Release: 10.2
Information in this document applies to any platform.

Symptoms

===================
-- Problem Statement:
ORA-12560 when trying to connect as sysdba after new install to create new database.

SQL*Plus: Release 10.2.0.4.0 - Production on Thu Nov 5 09:37:32 2009

Copyright (c) 1982, 2007, Oracle. All Rights Reserved.

specify a password for sys as parameter 1
Enter value for 1: xxxxxxxx
specify a password for system as parameter 2
Enter value for 2: xxxxxxxxxxx

ERROR:
ORA-12560: TNS:proto adapter error

SQL> spool /apps/oracle/RTM1U/u01/admin/create/CreateDB.log
SQL> startup nomount pfile="/apps/oracle/RTM1U/u01/admin/create/initRTM1U.ora";
ORA-12560: TNS:protocol adapter error
SQL> CREATE DATABASE "RTM1U"
2 MAXINSTANCES 32
3 MAXLOGHISTORY 50142
4 MAXLOGFILES 200
5 MAXLOGMEMBERS 5
6 MAXDATAFILES 500
7 DATAFILE '/apps/oracle/RTM1U/u02/data/system01.dbf' SIZE 1024M REUSE
8 EXTENT MANAGEMENT LOCAL

Changes

New install.

Cause

Installation issue. Binaries needed to be relinked.

Solution

-- To implement the solution, please execute the following steps::
Relink the Oracle binaries with 'relink all'

Handling Tricky Oracle Job Scheduling Problem!!

Oracle has made the life of database administrators easy by offering job queue that can be used for scheduling the operations that will be performed routinely in your Oracle databases. Oracle DBMS_JOB package is used for scheduling the Oracle jobs.

Error "ORA-27369: job of type EXECUTABLE failed with exit code: Not owner" When Using dbms_scheduler

Applies to: 
Oracle Server - Enterprise Edition - Version: 10.1.0.3.0
This problem can occur on any platform.

Resolving ORA-7279 or ORA-27146 errors when starting instance

Problem Description

When attempting to start an instance, you receive the following error:

  ORA-7279: spcre: semget error, unable to get first semaphore set

This error may possibly be accompanied by one or more of the following additional errors:

  ORA-600: internal error code, arguments [SKGMBUSY]
  SVR4 error: 28: no space left on device

Scheduled Job Running Shell Script Fails With ORA-27369

Applies to:


Oracle Server - Enterprise Edition - Version: 10.1.0.2 to 10.2.0.4
Oracle Server - Standard Edition - Version: 10.1.0.2 to 10.2.0.4
Sun Solaris SPARC (64-bit)
Linux x86
"ORA-27369: job of type EXECUTABLE failed with exit code: Unknown error" was still occurring for non oracle users running DBMS_SCHEDULER executed shell scripts. Problem was fixed when filesystem where ORACLE_HOME was mounted on was found to have been mounted w/ nosetuid. Changing mount option to setuid resolved problem

How To Resolve ORA-01595 and ORA-00600[4193] When Reported Together

Applies to:

Oracle Server - Enterprise Edition - Version: 8.1 to 9.2

Information in this document applies to any platform.

Goal:

How To Resolve ORA-01595 and ORA-00600[4193] When Reported Together 

ORA-01595: error freeing extent (2) of rollback segment (9) 

ORA-00607: Internal error occurred while making a change to a data block 

ORA-00600: internal error code, arguments: [4193], [64705], [64708], [], [], [], [], []