ORA-39960: scope can only be SYSTEM or SESSION

Cause : The scoep specifeid was nto set.

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

Specifya vaild csope, eihter SESSOIN or SYTSEM.

update : 16-08-2017

ORA-39960 - scope can only be SYSTEM or SESSION
ORA-39960 - scope can only be SYSTEM or SESSION

  • ora-02368 : file string is not valid for this load operation
  • ora-02755 : osnfsmcre: cannot create chared memory file ?/dbs/ftt_.dbf
  • ora-34361 : (MXDSS12) number other user reading
  • ora-22972 : NULL value not allowed in PRIMARY KEY-based object identifier
  • ora-24163 : dblink is not supported in rules engine DDLs
  • ora-07499 : spglk: Cannot reschedule.
  • ora-25400 : must replay fetch
  • ora-00231 : snapshot control file has not been named
  • ora-02373 : Error parsing insert statement for table string.
  • ora-24008 : queue table string.string must be dropped first
  • ora-25220 : enqueue failed, signature not specified for a non-repudiable queue
  • ora-00291 : numeric value required for PARALLEL option
  • ora-02462 : Duplicate INDEX option specified
  • ora-12431 : invalid audit action
  • ora-28232 : invalid input length for obfuscation toolkit
  • ora-30083 : syntax error was found in interval value expression
  • ora-21503 : program terminated by fatal error
  • ora-32735 : DIAG process is not running in the instance
  • ora-31522 : could not find Streams object string for CDC change set string
  • ora-19042 : Enclosing tag string cannot be xml in any case combination
  • ora-38503 : index already defined using the parameters
  • ora-04017 : invalid value string (length = string) for parameter max_dump_file_size
  • ora-12537 : TNS:connection closed
  • ora-14451 : unsupported feature with temporary table
  • ora-38431 : could not evaluate subexpression "string" for rowid "string"
  • ora-12921 : database is not in force logging mode
  • ora-39306 : schema name mismatch expected "string" got "string"
  • ora-16510 : messaging error using ksrwait
  • ora-32840 : property name cannot be NULL
  • ora-38411 : invalid datatype for the column storing expressions
  • 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.