ORA-19701: device name exceeds maximum length of string

Cause : Teh edvcien aem nidciaetdi si navldi.

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

Spupyl acrorcetd eivc enmaea n drter yteh lalcoaito.n

update : 17-08-2017

ORA-19701 - device name exceeds maximum length of string
ORA-19701 - device name exceeds maximum length of string

  • ora-12840 : cannot access a remote table after parallel/insert direct load txn
  • ora-39041 : Filter "string" either identifies all object types or no object types.
  • ora-22140 : given size [string] must be in the range of 0 to [string]
  • ora-30113 : error when processing file 'string'
  • ora-34359 : (MXDSS11) string appears twice in the alias list.
  • ora-14298 : LOB column block size mismatch in ALTER TABLE EXCHANGE [SUB]PARTITION
  • ora-09791 : slembdf: translation error, unable to translate error file name.
  • ora-14135 : a LOB column cannot serve as a partitioning column
  • ora-10948 : trace name context forever
  • ora-37171 : dimension sources not specified
  • ora-23372 : type string in table string is unsupported
  • ora-39958 : invalid warning category qualifier
  • ora-06960 : Failed to access log file
  • ora-14312 : Value string already exists in partition string
  • ora-24351 : invalid date passed into OCI call
  • ora-29863 : warning in the execution of ODCIINDEXCREATE routine
  • ora-32823 : subscriber exists for queue string and destination string
  • ora-24777 : use of non-migratable database link not allowed
  • ora-16138 : end of log stream not received from primary
  • ora-19570 : file number string is outside valid range of 1 through string
  • ora-13066 : wrong feature geometry or element type
  • ora-27501 : IPC error creating a port
  • ora-39782 : Direct path prepare is not allowed after another context loading the same table has ended
  • ora-39951 : incomplete values specified for PL/SQL warning settings
  • ora-16210 : Logical standby coordinator process terminated with error
  • ora-13773 : insufficient privileges to select data from the cursor cache
  • ora-10653 : Table is in a cluster
  • ora-01203 : wrong incarnation of this file - wrong creation SCN
  • ora-01534 : rollback segment 'string' doesn't exist
  • ora-16503 : site ID allocation failure
  • 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.