ORA-13410: invalid layerNumbers or bandNumbers parameter

Cause : The layerNumbers or bandNumbers parameter was invalid.

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

Check the documentation and make sure the layerNumbers or bandNumbers parameter is valid.

update : 25-04-2017

ORA-13410 - invalid layerNumbers or bandNumbers parameter
ORA-13410 - invalid layerNumbers or bandNumbers parameter

  • ora-28120 : driving context already exists
  • ora-01424 : missing or illegal character following the escape character
  • ora-06323 : IPA: Cause event error
  • ora-22286 : insufficient privileges on file or directory to perform string operation
  • ora-25106 : only one of PARALLEL or NOPARALLEL clause may be specified
  • ora-30731 : scope constraint not allowed on nested table column when the nested table is being created
  • ora-16172 : archive logs detected beyond Terminal End-Of-Redo
  • ora-14085 : partitioned table cannot have column with LONG datatype
  • ora-28174 : Kerberos ticket not provided by proxy
  • ora-32775 : cannot change size attributes of read only tablespace string
  • ora-19755 : could not open change tracking file
  • ora-00355 : change numbers out of order
  • ora-30695 : JDWP message format problem
  • ora-24080 : unschedule_propagation pending for QUEUE string and DESTINATION string
  • ora-02782 : Both read and write functions were not specified
  • ora-12679 : Native services disabled by other process but required
  • ora-36718 : (XSALLOC00) You do not have the necessary permissions to use AGGMAP workspace object.
  • ora-00021 : session attached to some other process; cannot switch session
  • ora-39014 : One or more workers have prematurely exited.
  • ora-10940 : trace name context forever
  • ora-34001 : (MODCOMP14) Concat leaf dimension workspace object already is used in a DIMENSION statement, either explicitly or as a leaf of another concat dimension.
  • ora-13834 : name of SQL profile to be cloned must be provided
  • ora-31100 : XDB Locking Internal Error
  • ora-00443 : background process "string" did not start
  • ora-12990 : duplicate option specified
  • ora-24812 : character set conversion to or from UCS2 failed
  • ora-12032 : cannot use rowid column from materialized view log on "string"."string"
  • ora-30105 : 'string' is not a legal boolean for 'string'
  • ora-31403 : change table string already contains a column string
  • ora-12085 : materialized view log on "string"."string" already has object id
  • 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.