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 : 26-04-2017
ORA-16197

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

  • ora-06813 : TLI Driver: the configured ethernet address is incorrect
  • ora-24413 : Invalid number of sessions specified
  • ora-40223 : data mining model import failed, job name=string, error=string
  • ora-38440 : attribute set string does not exist
  • ora-01530 : a database already mounted by the instance
  • ora-30341 : dropped level has references
  • ora-40214 : duplicate setting: string
  • ora-38758 : cannot flashback data file string; restored since last recovery
  • ora-06605 : LU6.2 Driver: Unexpected line turnaround
  • ora-01910 : TABLES keyword expected
  • ora-26051 : internal error parsing packed decimal format string
  • ora-13260 : layer table string does not exist
  • ora-39165 : Schema string was not found.
  • ora-02220 : invalid MINEXTENTS storage option value
  • ora-04085 : cannot change the value of an OLD reference variable
  • ora-39775 : direct path API commit not allowed due to previous fatal error
  • ora-16231 : DDL barrier
  • ora-02442 : Cannot drop nonexistent unique key
  • ora-31693 : Table data object string failed to load/unload and is being skipped due to error: string
  • ora-12684 : encryption/crypto-checksumming: Diffie-Hellman seed too small
  • ora-07214 : slgunm: uname error, unable to get system information.
  • ora-24503 : codepoint length overflows for piecewise operation
  • ora-07240 : slemrd: seek error.
  • ora-14509 : specified VALIDATE INTO table form incorrect
  • ora-23431 : wrong state: string
  • ora-27417 : BYWEEKNO clause is only supported when FREQ=YEARLY
  • ora-23622 : Operation string.string.string is in progress.
  • ora-31524 : could not find change set string for CDC change table string.string
  • ora-39133 : object type "string"."string" already exists with different typeid
  • ora-13354 : incorrect offset in ELEM_INFO_ARRAY
  • 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.