ORA-02300: invalid value for OIDGENERATORS

Cause : A number was not specified for the value of OIDGENERATORS.

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

Specify a number for OIDGENERATORS.

update : 24-07-2017
ORA-02300

ORA-02300 - invalid value for OIDGENERATORS
ORA-02300 - invalid value for OIDGENERATORS

  • ora-19104 : invalid XQueryX: missing attribute string
  • ora-01898 : too many precision specifiers
  • ora-19692 : missing creation stamp on piece string
  • ora-30563 : outer join operator (+) not allowed in select-list
  • ora-01256 : error in locking database file string
  • ora-01932 : ADMIN option not granted for role 'string'
  • ora-02031 : no ROWID for fixed tables or for external-organized tables
  • ora-39129 : Object type string not imported. Name conflicts with the master table
  • ora-29271 : not connected
  • ora-31665 : mode can only be defaulted for IMPORT and SQL_FILE operations
  • ora-26710 : incompatible version marker encountered during Capture
  • ora-38494 : column in the table alias and an attribute have matching names
  • ora-01624 : log string needed for crash recovery of instance string (thread string)
  • ora-29502 : NAMED keyword required in CREATE JAVA RESOURCE
  • ora-01900 : LOGFILE keyword expected
  • ora-29379 : resource plan string is involved in a loop in top-plan string
  • ora-29512 : incorrectly formed name resolver specification
  • ora-24354 : number fetched too large to fit in COBOL display type buffer.
  • ora-29255 : Cursor contains both bind and define arrays which is not permissible
  • ora-16775 : target standby database in broker operation has potential data loss
  • ora-16088 : archive log has not been completely archived
  • ora-23343 : no match for specified conflict resolution information
  • ora-06251 : NETNTT: cannot translate address file name
  • ora-08210 : Requested I/O error
  • ora-36664 : (XSDPART02) You must specify a partitioning method and one or more partition dimensions when defining a PARTITION TEMPLATE.
  • ora-30695 : JDWP message format problem
  • ora-13408 : invalid blockSize storage parameter
  • ora-12672 : Database logon failure
  • ora-16228 : Insufficient recovery for logical standby
  • ora-16061 : Log file status has changed
  • 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.