ORA-28038: disallow O2LOGON

Cause : turn off O2LOGON

Action - How to fix it : DBA Scripts :: www.high-oracle.com/scripts


update : 27-06-2017

ORA-28038 - disallow O2LOGON
ORA-28038 - disallow O2LOGON

  • ora-24350 : OCI call not allowed
  • ora-01334 : invalid or missing logminer dictionary processes context
  • ora-16001 : database already open for read-only access by another instance
  • ora-02334 : cannot infer type for column
  • ora-12489 : default label not within clearance range
  • ora-28673 : Merge operation not allowed on an index-organized table
  • ora-01600 : at most one "string" in clause "string" of string
  • ora-06031 : NETDNT: connect failed, unrecognized object name
  • ora-16571 : Data Guard configuration file creation failure
  • ora-19210 : column 'string', specified to be a key or update column for DBMS_XMLSTORE, does not not exist in table 'string'
  • ora-00910 : specified length too long for its datatype
  • ora-19960 : Internal use only
  • ora-06503 : PL/SQL: Function returned without value
  • ora-12827 : insufficient parallel query slaves available
  • ora-33302 : (DBVALID01) SEVERE ERROR: Record number multiply used.
  • ora-36671 : (XSDPART09) Leaves of workspace object have different datatypes. A partition dimension cannot have more than one datatype when RANGE partitioning is used.
  • ora-38703 : Type string in header is not a flashback database log file.
  • ora-32773 : operation not supported for smallfile tablespace string
  • ora-29394 : session id string and serial# string do not exist
  • ora-22971 : invalid datatype for PRIMARY KEY-based object identifier
  • ora-33022 : (XSAGDNGL10) The measure dimension workspace object must be a TEXT or ID base dimension that does not dimension AGGMAP workspace object, but is in the same analytic workspace.
  • ora-31637 : cannot create job string for user string
  • ora-27478 : job "string.string" is running
  • ora-01159 : file is not from same database as previous files - wrong database id
  • ora-30507 : normal triggers cannot be based on a schema or a database
  • ora-12643 : Client received internal error from server
  • ora-02188 : Cannot enable instance publicly
  • ora-19902 : incarnation key string not found
  • ora-06805 : TLI Driver: could not send datagram SAP packet for SPX
  • Oracle Database Error Messages

    Oracle Database High Availability Any organization evaluating a database solution for enterprise data must also evaluate the High Availability (HA) capabilities of the database. Data is one of the most critical business assets of an organization. If this data is not available and/or not protected, companies may stand to lose millions of dollars in business downtime as well as negative publicity. Building a highly available data infrastructure is critical to the success of all organizations in today's fast moving economy.

    Well, the reason for above error is that i have taken the above script from a 11g database and running it on 10g database. 11g has bring some changes in password management. Below code is executed on 11g and user created successfully, which is expected result.