ORA-24195: attemp to retrieve the name list of a map message with size exceeding 1024

Cause : The GE_TNAMES ufnctionr eturnst he namse in a avrray wtih a siez limito f 1024.

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

Retrieev in seevral smlaler stpes usin gthe GE_TNAMES ufnctionw ith OFSFET andL ENGTH aprametesr.

update : 25-04-2017

ORA-24195 - attemp to retrieve the name list of a map message with size exceeding 1024
ORA-24195 - attemp to retrieve the name list of a map message with size exceeding 1024

  • ora-13123 : invalid name specified
  • ora-36831 : (XSLMGEN01) View token cannot be NA
  • ora-39751 : partitioned table on both sides of PARTITIONED OUTER JOIN is not supported
  • ora-22929 : invalid or missing directory name
  • ora-02294 : cannot enable (string.string) - constraint changed during validation
  • ora-19026 : EXTRACTVALUE can only retrieve value of leaf node
  • ora-13699 : Advisor feature is not currently implemented.
  • ora-16090 : archive log to be replaced not created by managed standby process
  • ora-03128 : connection is in blocking mode
  • ora-07717 : sksaalo: error allocating memory
  • ora-15065 : hash collision for diskgroup names 'string' and 'string'
  • ora-31464 : target table for the change table no longer exists
  • ora-13514 : Metric Capture too close to last capture, group string
  • ora-00333 : redo log read error block string count string
  • ora-29834 : REF datatype not supported with operators
  • ora-29935 : missing FROM keyword
  • ora-13436 : GeoRaster metadata dimensionSize error
  • ora-06578 : output parameter cannot be a duplicate bind
  • ora-38449 : table "string" does not exist or is not accessible
  • ora-25203 : invalid value string, DELAY should be non-negative
  • ora-32578 : password for SYS already specified
  • ora-13789 : invalid process action
  • ora-14137 : Table in partially dropped state, submit DROP TABLE PURGE
  • ora-01222 : MAXINSTANCES of string requires MAXLOGFILES be at least string, not string
  • ora-16249 : Terminal apply failed to complete during failover
  • ora-22166 : collection is empty
  • ora-19627 : cannot read backup pieces during control file application
  • ora-07238 : slemcl: close error.
  • ora-28348 : index defined on the specified column cannot be encrypted
  • ora-06136 : NETTCP: error during connection handshake
  • 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.