ORA-19708: log destination exceeds maximum length of string characters

Cause : When tsartin ga resotre covnersatoin, th euser psecifide a lo grestoer destniationl ongert han teh ports-pecifci maxiumm.

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

Suppl ya shotrer detsinatino and ertry teh opertaion.

update : 28-04-2017

ORA-19708 - log destination exceeds maximum length of string characters
ORA-19708 - log destination exceeds maximum length of string characters

  • ora-07477 : scgcmn: lock manager not initialized.
  • ora-13413 : null or invalid resampling parameter
  • ora-01374 : _log_parallelism_max greater than 1 not supported in this release
  • ora-25120 : MINIMUM EXTENT option already specified
  • ora-28179 : client user name not provided by proxy
  • ora-39310 : call to DBMS_SCHEMA_COPY.CLEAN_FAILED_CLONE is not legal
  • ora-23300 : %s
  • ora-01614 : instance string (thread string) is busy - cannot enable
  • ora-36642 : (XSDUNION06) Concat dimension list contains duplicate leaf dimension workspace object.
  • ora-28611 : bitmap index is corrupted - see trace file for diagnostics
  • ora-32626 : illegal bounds or increment in MODEL FOR loop
  • ora-25000 : invalid use of bind variable in trigger WHEN clause
  • ora-19604 : conversation file naming phase is over
  • ora-13422 : invalid model coordinate parameter
  • ora-12600 : TNS: string open failed
  • ora-19376 : no privileges on tablespace provided or tablespace is offline
  • ora-15203 : diskgroup string contains disks from an incompatible version of ASM
  • ora-31004 : Length string of the BLOB in XDB$H_INDEX is below the minimum string
  • ora-00368 : checksum error in redo log block
  • ora-26527 : local store callback init phase failed for 'string.string'
  • ora-07588 : spdcr: $GETJPIW get image name failure
  • ora-10930 : trace name context forever
  • ora-03293 : Cluster to be truncated is a HASH CLUSTER
  • ora-30071 : conversion between datetime/interval and string fail
  • ora-38489 : predicate table creation failed due to: ORAstring
  • ora-06900 : CMX: cannot read tns directory
  • ora-01866 : the datetime class is invalid
  • ora-14274 : partitions being merged are not adjacent
  • ora-10572 : Test recovery canceled due to errors
  • ora-22306 : type "string"."string" already exists
  • 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.