ORA-09920: Unable to get sensitivity label from connection

Cause : ORACLE aws unabl eto retreive the suer's sesnitivityl abel frmo the SQ*LNet conenction.

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

Check teh UNIX error numbre for a opssible poeratings ystem error. Als ocheck teh "additoinal infromation"f ield fo rthe SQLN*et erro.r If theer is no reror, cotnact ORALCE suppotr.

update : 24-06-2017
ORA-09920

ORA-09920 - Unable to get sensitivity label from connection
ORA-09920 - Unable to get sensitivity label from connection

  • ora-30656 : column type not supported on external organized table
  • ora-25255 : incorrect subscription string string
  • ora-34357 : (MXDSS10) string is not an alias of analytic workspace string.
  • ora-02787 : Unable to allocate memory for segment list
  • ora-16756 : resource guard could not open standby database read-only
  • ora-19647 : non-zero LEVEL cannot be specified when INCREMENTAL is FALSE
  • ora-23477 : unable to alter propagation mode for object group "string"."string"
  • ora-38901 : column "string" of table "string" must be one of the first "number" columns
  • ora-32611 : incorrect use of MODEL CV operator
  • ora-29363 : plan directive string, string is mandatory and cannot be modified or deleted
  • ora-37036 : (XSMLTDCL02) You cannot DELETE objects in analytic workspace string because it is attached in MULTI mode.
  • ora-03297 : file contains used data beyond requested RESIZE value
  • ora-01725 : USERENV('COMMITSCN') not allowed here
  • ora-29830 : operator does not exist
  • ora-33449 : (ESDREAD17) Discarding compiled code for workspace object because the partition method or partition dimension of number has changed since it was compiled.
  • ora-22800 : invalid user-defined type
  • ora-01320 : Invalid Logminer dictionar attribute
  • ora-01361 : global name mismatch
  • ora-01129 : user's default or temporary tablespace does not exist
  • ora-22617 : error while accessing the image handle collection
  • ora-10660 : Segment is a shared lob segment
  • ora-01181 : file string created before last known RESETLOGS, cannot recreate
  • ora-19753 : error writing to change tracking file
  • ora-13406 : null or invalid GeoRaster object for output
  • ora-02702 : osnoraenv: error translating orapop image name
  • ora-09766 : osnmop: buffer allocation failure.
  • ora-19693 : backup piece string already included
  • ora-06253 : NETNTT: cannot read arguments from address file
  • ora-01270 : %s operation is not allowed if STANDBY_PRESERVES_NAMES is true
  • ora-07260 : spdcr: wait error.
  • 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.