ORA-19378: invalid mode

Cause : The user specified an invalid mode argument to the capture function.

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

Provide a mode argument that was defined in the dbmssqlt file

update : 27-04-2017
ORA-19378

ORA-19378 - invalid mode
ORA-19378 - invalid mode

  • ora-38497 : Expression Filter index does not exist
  • ora-14609 : Tablespace was not specified for the previous lob segments of column string in template but is specified for string
  • ora-29372 : identifier string is too long; it must be less than string characters
  • ora-15182 : ASMLIB [string] version mismatch, ORACLE version [string]
  • ora-24317 : define handle used in a different position
  • ora-24755 : OCI_TRANS_NOMIGRATE, OCI_TRANS_JOIN options are not supported
  • ora-30400 : identical JOIN KEY clauses
  • ora-12452 : label tag string already exists
  • ora-22606 : pickler image handle [string] is not well-formed
  • ora-06775 : TLI Driver: error reading break mode
  • ora-37004 : (AWLISTALL02) number reader
  • ora-30484 : missing window specification for this function
  • ora-36886 : (XSSRF05) Error rewritting OLAP DML expression. Rewritten expression is greater than number bytes
  • ora-00407 : rolling upgrade from release string.string to string.string is not allowed
  • ora-32011 : cannot restore SPFILE to location already being used by the instance
  • ora-27489 : unable to process job "string.string" from job class "string"
  • ora-30966 : error detected in the XML Index layer
  • ora-16590 : Data Guard configuration does not contain a primary database
  • ora-12602 : TNS: Connection Pooling limit reached
  • ora-23365 : site string does not exist
  • ora-19881 : Corrupted space bitmap for datafile string, block string backup aborted
  • ora-26077 : direct path column array is not initialized
  • ora-19525 : temporary file for the clone database must be renamed
  • ora-30467 : internal data for filter number string is inconsistent
  • ora-00485 : DIAG process terminated with error string
  • ora-07842 : sllfcl: SYS$CLOSE failure
  • ora-30060 : Internal event for RECO tracing
  • ora-00072 : process "string" is not active
  • ora-00313 : open failed for members of log group string of thread string
  • ora-31535 : cannot support change source string in this configuration
  • 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.