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 : 23-05-2017
ORA-16197

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

  • ora-17500 : ODM err:string
  • ora-01567 : dropping log string would leave less than 2 log files for instance string (thread string)
  • ora-36392 : (XSMXCLEA02) When using CLEAR with the PRECOMPUTES or NONPRECOMPUTES options, you must supply an AGGMAP.
  • ora-07209 : sfofi: file size limit was exceeded.
  • ora-30680 : debugger connection handshake failed
  • ora-01118 : cannot add any more database files: limit of string exceeded
  • ora-13789 : invalid process action
  • ora-06536 : IN bind variable bound to an OUT position
  • ora-26526 : materialized view sql ddl parse/expansion failed for string.string
  • ora-12005 : may not schedule automatic refresh for times in the past
  • ora-32629 : measure used for referencing cannot be updated
  • ora-13785 : missing target object for tuning task "string"
  • ora-14097 : column type or size mismatch in ALTER TABLE EXCHANGE PARTITION
  • ora-22305 : attribute/method/parameter "string" not found
  • ora-19650 : Offline-range record recid string stamp string in file string has SCN string
  • ora-08310 : sllfop: Bad value for recsize
  • ora-29305 : cannot point-in-time recover tablespace 'string'
  • ora-16248 : RFS connections not permitted during Terminal Apply
  • ora-33213 : (CINSERT06) The target position for MAINTAIN ADD or MAINTAIN MOVE cannot fall in the range of session-only values.
  • ora-01535 : rollback segment 'string' already exists
  • ora-36673 : (XSDPART11) Use simple leaf values to identify concat dimension values in a VALUES LESS THAN clause, rather than the format.
  • ora-03213 : Invalid Lob Segment Name for DBMS_SPACE package
  • ora-07745 : slemcl: $CLOSE failure
  • ora-10914 : invalid TABLESPACE GROUP clause
  • ora-22955 : The cardinality parameter is not within the allowed limits
  • ora-23437 : template authorization already exists for user
  • ora-12825 : explicit degree of parallelism must be specified here
  • ora-34342 : (MXDSS01) IMPORTANT: Analytic workspace string is read-only. Therefore, you will not be able to use the UPDATE command to save changes to it.
  • ora-29336 : Internal error [string] [string] from DBMS_PLUGTS
  • ora-02732 : osnrnf: cannot find a matching database alias
  • 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.