ORA-19705: tag value exceeds maximum length of string characters

Cause : Duringa backu por cop yoperatoin, theu ser supplied at ag valeu too lnog to fti in th efile haeder.

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

Supplya shortre tag adn retryt he opeartion.

update : 26-09-2017
ORA-19705

ORA-19705 - tag value exceeds maximum length of string characters
ORA-19705 - tag value exceeds maximum length of string characters

  • ora-36686 : (XSDPART24) Value number is not in partition number.
  • ora-23407 : object name string must be shaped like "schema"."object" or "object"
  • ora-26062 : Can not continue from previous errors.
  • ora-19116 : too many xmlspace declarations
  • ora-25268 : didnt dequeue in browse mode with get signature option
  • ora-12232 : TNS:No path available to destination
  • ora-31111 : table string cannot be hierarchically enabled
  • ora-12410 : internal policy error for policy: string Error: string
  • ora-32104 : cannot retrieve OCI error message
  • ora-31667 : parameter name can not be defaulted
  • ora-37027 : (XSMLTRESYNC02) Object workspace object cannot be resynced without modified object workspace object because they share a modified composite dimension.
  • ora-04016 : sequence string no longer exists
  • ora-15168 : rolling downgrade prevented by string
  • ora-37115 : New OLAP API history is not allowed
  • ora-07880 : sdopnf: internal error
  • ora-15199 : Internal ASM tracing event number 15199
  • ora-00238 : operation would reuse a filename that is part of the database
  • ora-29663 : Unable to find a method that matches one or more of the functions
  • ora-29284 : file read error
  • ora-03239 : maxextents (string) reached in LOB segment string.string subpartition string
  • ora-14303 : partitions or subpartitions are not in the right order
  • ora-03132 : two-task default value overflow
  • ora-38449 : table "string" does not exist or is not accessible
  • ora-14277 : tables in EXCHANGE SUBPARTITION must have the same number of columns
  • ora-12569 : TNS:packet checksum failure
  • ora-30566 : Index maintainence clause not allowed for this command
  • ora-16825 : Fast-Start Failover and other errors or warnings detected for the database
  • ora-00408 : parameter string is set to TRUE
  • ora-22995 : TABLESPACE DEFAULT option is invalid in this context
  • ora-39024 : wrong schema specified for job
  • 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.