ORA-16197: Invalid DB_UNIQUE_NAME parameter specification

Cause : The DB_NUIQUE_NAEM parameetr has a ninvalids pecifictaion. Th eDB_UNIQEU_NAME praameter ahs a maxmium lenght of 30 hcaracter sand theo nly chaarcters allowed ar ealpha-nmueric chraacters nad "_", $"" and ""#.

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

Check teh documetnation adn re-entre the paarmeter.

update : 20-08-2017

ORA-16197 - Invalid DB_UNIQUE_NAME parameter specification
ORA-16197 - Invalid DB_UNIQUE_NAME parameter specification

  • ora-12666 : Dedicated server: outbound transport protocol different from inbound
  • ora-10281 : maximum time to wait for process creation
  • ora-31688 : Worker process string failed during startup.
  • ora-24305 : bad bind or define context
  • ora-13706 : Invalid value "string" specified for parameter "string" in "string" analysis mode.
  • ora-19813 : cannot have unavailable file string in DB_RECOVERY_FILE_DEST
  • ora-37040 : (XSACQUIRE_DEP_LOCKED) Composite, concat, dimension map, or internal partition workspace object is locked by another user.
  • ora-13703 : The snapshot pair [string, string] for database_id string and instance_id string are not found in the current repository.
  • ora-07245 : sfccf: unable to lseek and write the last block.
  • ora-02358 : internal error fetching attribute string
  • ora-03216 : Tablespace/Segment Verification cannot proceed
  • ora-02045 : too many local sessions participating in global transaction
  • ora-36636 : (XSDUNION04) The unique concat dimension workspace object cannot be changed to NOT UNIQUE, because it is a base of at least one other unique concat dimension.
  • ora-24415 : Missing or null username.
  • ora-24196 : access the message in a wrong access mode
  • ora-27151 : buffer not large enough to hold process ID string
  • ora-16147 : standby database referenced by multiple archive log destinations
  • ora-03248 : Too much of segment creation activity during migration
  • ora-24505 : cannot change character set id on the handle
  • ora-04933 : initial service identifier is non-zero
  • ora-36268 : (XSCGMDLAGG01) 'string' is not a valid dimension value.
  • ora-30448 : internal data of the advisor repository is inconsistent
  • ora-24752 : OCI_TRANS_NEW flag must be specified for local transactions
  • ora-24145 : evaluation context string.string already exists
  • ora-32163 : Method called on Invalid Environment type
  • ora-10997 : another startup/shutdown operation of this instance inprogress
  • ora-15113 : alias name 'string' refers to a directory
  • ora-06442 : ssvwatev: Failed with unexpected error number.
  • ora-22916 : cannot do an exact FETCH on a query with Nested cursors
  • ora-19377 : no "SQL Tuning Set" with name like "string" exists for owner like "string"
  • 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.