Oracle Error Messages: 05/07/12

Monday 7 May 2012

ORA-28052: the account is disabled

ORA-28052: the account is disabled

Cause: The enterprise user s account in the directory has been disabled.

Action: Contact the directory administrator.

ORA-28051: the account is locked

ORA-28051: the account is locked

Cause: The enterprise user has consecutively entered the wrong password for maximum number of times specified in the realm s password policy profile.

Action: Contact the directory administrator.

ORA-28049: the password has expired

ORA-28049: the password has expired

Cause: The enterprise user s password has expired and the password needs to be changed.

Action: change the password in the directory or contact the directory administrator.

ORA-28048: database is a member of multiple enterprise domains in OID

ORA-28048: database is a member of multiple enterprise domains in OID

Cause: An enterprise user login was attempted on a database that is a member of multiple enterprise domains in OID.

Action: An administrator should put the database into only one enterprise domain in OID, and then the user should reconnect.

ORA-28047: database is not a member of any enterprise domain in OID

ORA-28047: database is not a member of any enterprise domain in OID

Cause: An enterprise user login was attempted on a database that is not a member of any enterprise domain in OID.

Action: An administrator should put the database into an enterprise domain in OID, and then the user should reconnect.

ORA-28046: Password change for SYS disallowed

ORA-28046: Password change for SYS disallowed

Cause: REMOTE_LOGIN_PASSWORDFILE is set to SHARED, prohibiting SYS password changes.

Action: Change setting of REMOTE_LOGIN_PASSWORDFILE to EXCLUSIVE or NONE.

ORA-28045: SSL authentication between database and OID failed

ORA-28045: SSL authentication between database and OID failed

Cause: Server failed to authenticate itself to the Directory.

Action: Make sure the sqlnet.ora used is pointing to the wallet with the right certificate.

ORA-28044: unsupported directory type

ORA-28044: unsupported directory type

Cause: The database tried to work with a directory which is not OID.

Action: Enterprise User Security works only with Oracle Internet Directory. Update the ldap.ora file to reflect an appropriate OID.

ORA-28043: invalid bind credentials for DB-OID connection

ORA-28043: invalid bind credentials for DB-OID connection

Cause: The Database password stored in the wallet did not match the one in OID .

Action: Use DBCA to reset the database password so that it is the same in database wallet and in OID.

ORA-28042: Server authentication failed

ORA-28042: Server authentication failed

Cause: Server failed to authenticate itself to the client

Action: Confirm that the server is a valid database server.

ORA-28041: Authentication protocol internal error

ORA-28041: Authentication protocol internal error

Cause: Authentication protocol failed with an internal error

Action: none

ORA-28040: No matching authentication protocol

ORA-28040: No matching authentication protocol

Cause: No acceptible authentication protocol for both client and server

Action: Administrator should set SQLNET_ALLOWED_LOGON_VERSION parameter on both client and servers to values that matches the minimum version supported in the system.

ORA-28039: cannot validate Kerberos service ticket

ORA-28039: cannot validate Kerberos service ticket

Cause: The Kerberos service ticket provided was invalid or expired

Action: Provide a valid, unexpired service ticket.

ORA-28038: disallow O2LOGON

ORA-28038: disallow O2LOGON

Cause: turn off O2LOGON

Action: none

ORA-28037: Cannot Get Session Key for RACF Authentication

ORA-28037: Cannot Get Session Key for RACF Authentication

Cause: Client and server cannot negotiate shared secret during logon

Action: User should not see this error. Please contact your system administrator

ORA-28035: Cannot Get Session Key for Authentication

ORA-28035: Cannot Get Session Key for Authentication

Cause: Client and server cannot negotiate shared secret during logon

Action: User should not see this error. Please contact your system administrator

ORA-28031: maximum of string enabled roles exceeded

ORA-28031: maximum of string enabled roles exceeded

Cause: The user attempted to enable too many roles.

Action: Enable fewer roles.

ORA-28030: Server encountered problems accessing LDAP directory service

ORA-28030: Server encountered problems accessing LDAP directory service

Cause: Unable to access LDAP directory service

Action: Please contact your system administrator

ORA-28029: could not authorize remote server for user string

ORA-28029: could not authorize remote server for user string

Cause: During the course of opening a privileged database link, the remote server was found to lack the necessary authorizations to connect as the current global user. This may be because the server was not authorized by the network security service. Or it may be because the local server is restricting access by the remote server using the DBMS_SECURITY_DOMAINS_ADMIN package.

Action: Grant the remote server the proper authorization to connect as the given global user, and check that the local server is not restricting access.

ORA-28028: could not authenticate remote server

ORA-28028: could not authenticate remote server

Cause: During the course of opening a privileged database link, the remote server was not securely identified using the network security service. Additional errors should follow.

Action: Consult the network security service documentation on how to properly configure the remote server.

ORA-28027: privileged database links may be used by global users

ORA-28027: privileged database links may be used by global users

Cause: Only users IDENTIFIED GLOBALLY may use a privileged database link.

Action: Either change the user to a global user or try to use a different database link.

ORA-28026: user with same external name already exists

ORA-28026: user with same external name already exists

Cause: The external name specified for the user being created or altered already exists for another user.

Action: External names must be unique among users. Specify another.

ORA-28025: missing or null external name

ORA-28025: missing or null external name

Cause: The IDENTIFIED EXTERNALLY AS or IDENTIFIED GLOBALLY AS clause was specified with a valid external name.

Action: Provide a valid external name.

ORA-28024: must revoke grants of external roles to this role or user

ORA-28024: must revoke grants of external roles to this role or user

Cause: The user or role altered to IDENTIFIED GLOBALLY has external roles directly granted - these must be revoked, since external roles cannot be granted to global users or roles.

Action: Use REVOKE to revoke the external roles from the user or role to be ALTERed.

ORA-28023: must revoke grants of this role to other user(s) first

ORA-28023: must revoke grants of this role to other user(s) first

Cause: The role altered to IDENTIFIED GLOBALLY was granted to one or more other users and or or roles. Global roles cannot be granted to any user or role.

Action: Use REVOKE to revoke the role from other users or roles first.

ORA-28022: cannot grant external roles to global user or role

ORA-28022: cannot grant external roles to global user or role

Cause: A role granted was IDENTIFIED EXTERNALLY. External roles cannot be granted to global users or global roles.

Action: Use ALTER ROLE to change the type of the role being granted (from IDENTIFIED EXTERNALLY to other, such as IDENTIFIED BY password), or use ALTER ROLE or ALTER USER to change the type of the user or role that is the grantee.

ORA-28021: cannot grant global roles

ORA-28021: cannot grant global roles

Cause: A role granted was IDENTIFIED GLOBALLY. Global roles can only be granted via a central authority for the domain.

Action: Use ALTER ROLE to change the type of role (from IDENTIFIED GLOBALLY to other, such as IDENTIFIED BY password), or allocate it to a global user via the central authority.

ORA-28020: IDENTIFIED GLOBALLY already specified

ORA-28020: IDENTIFIED GLOBALLY already specified

Cause: The IDENTIFIED GLOBALLY clause was specified twice.

Action: Use only one IDENTIFIED GLOBALLY clause.

ORA-28012: Manual commit not allowed here

ORA-28012: Manual commit not allowed here

Cause: An attempt was made to commit a non-autonomous transaction from within a change password trigger or password verification routine

Action: Remove the COMMIT from the password trigger or password verification routine

ORA-28011: the account will expire soon; change your password now

ORA-28011: the account will expire soon; change your password now

Cause: The user s account is marked for expiry; the expiry period is unlimited.

Action: Change the password or contact the DBA.

ORA-28010: cannot expire external or global accounts

ORA-28010: cannot expire external or global accounts

Cause: If a user account is created as IDENTIFIED EXTERNALLY, or IDENTIFIED GLOBALLY, this account cannot be expired

Action: Try to expire the password of the user that has database password

ORA-28009: connection as SYS should be as SYSDBA or SYSOPER

ORA-28009: connection as SYS should be as SYSDBA or SYSOPER

Cause: connect SYS or lamp;lt;lamp;nbsp;passwordlamp;gt; is no longer a valid syntax

Action: Try connect SYS or lamp;lt;lamp;nbsp;passwordlamp;gt; as SYSDBA or connect SYS or lamp;lt;lamp;nbsp;passwordlamp;gt; as SYSOPER

ORA-28008: invalid old password

ORA-28008: invalid old password

Cause: old password supplied is wrong; Hence user cannot be authenticated using old password

Action: Supply the correct old password for authentication

ORA-28007: the password cannot be reused

ORA-28007: the password cannot be reused

Cause: The password cannot be reused for the specified number of days or for the specified nunmber of password changes

Action: Try the password that you have not used for the specified number of days or the specified number of password changes Refer to the password parameters in the CREATE PROFILE statement

ORA-28006: conflicting values for parameters string and string

ORA-28006: conflicting values for parameters string and string

Cause: The parameters PASSWORD_REUSE_TIME and PASSWORD_REUSE_ MAX cannot both be set. One parameter should be unlimited while other is set

Action: Set one value to UNLIMITED explicitly

ORA-28005: invalid logon flags

ORA-28005: invalid logon flags

Cause: The flags are not properly set or conflicting flags are set in making calls

Action: Call the function with appropriate flags set.

ORA-28004: invalid argument for function specified in PASSWORD_VERIFY_ FUNCTION string

ORA-28004: invalid argument for function specified in PASSWORD_VERIFY_ FUNCTION string

Cause: The password verification function does not have the required number and type of input or output arguments and or or the return argument

Action: Check the manual to find out the format of the password verification function

ORA-28003: password verification for the specified password failed

ORA-28003: password verification for the specified password failed

Cause: The new password did not meet the necessary complexity specifications and the password_verify_function failed

Action: Enter a different password. Contact the DBA to know the rules for choosing the new password

ORA-28002: the password will expire within string days

ORA-28002: the password will expire within string days

Cause: The user s account is about to about to expire and the password needs to be changed

Action: change the password or contact the DBA

ORA-28001: the password has expired

ORA-28001: the password has expired

Cause: The user s account has expired and the password needs to be changed

Action: change the password or contact the DBA

ORA-28000: the account is locked

ORA-28000: the account is locked

Cause: The user has entered wrong password consequently for maximum number of times specified by the user s profile parameter FAILED_LOGIN_ATTEMPTS, or the DBA has locked the account

Action: Wait for PASSWORD_LOCK_TIME or contact DBA

ORA-27550: Target ID protocol check failed. tid vers=number, type=number, remote instance number=number, local instance number=number

ORA-27550: Target ID protocol check failed. tid vers=number, type=number, remote instance number=number, local instance number=number

Cause: The local Oracle Real Application Cluster instance and remote instance are running with incompatible implementation of the inter-instance IPC protocol library. A misconfiguration or installation error occurred.

Action: Check additional error messages in the alert log and the process trace file.