ORA-34900: (PPWKDAYS00) At least 7 day names must be given. Only number were provided.

Cause : There must be at least one name for each day. Not enough names were provided.

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

Make sure there are at least 7 names in the string.

update : 24-07-2017
ORA-34900

ORA-34900 - (PPWKDAYS00) At least 7 day names must be given. Only number were provided.
ORA-34900 - (PPWKDAYS00) At least 7 day names must be given. Only number were provided.

  • ora-06413 : Connection not open.
  • ora-03242 : Tablespace migration retried 500 times
  • ora-14298 : LOB column block size mismatch in ALTER TABLE EXCHANGE [SUB]PARTITION
  • ora-32620 : illegal subquery within MODEL rules
  • ora-24810 : attempting to write more data than indicated
  • ora-19045 : character set id specified for XMLSerialize not valid
  • ora-38401 : synonym string not allowed
  • ora-01940 : cannot drop a user that is currently connected
  • ora-30564 : Index maintainence clause not allowed for ADD partition to RANGE partitioned tables
  • ora-12915 : Cannot alter dictionary managed tablespace to read write
  • ora-31500 : change source string is not a ManualLog change source
  • ora-01417 : a table may be outer joined to at most one other table
  • ora-36726 : (XSALERR00) The character 'character' is not a valid format specifier for the ALLOCATE error log.
  • ora-00610 : Internal error code
  • ora-31444 : parameter error while acquiring lock on string
  • ora-31027 : Path name or handle string does not point to a resource
  • ora-30074 : GLOBAL partitioned index on TIME/TIMESTAMP WITH TIME ZONE not allowed
  • ora-14003 : GLOBAL clause contradicts previosly specified LOCAL clause
  • ora-36276 : (XSCGMDLAGG06) The current operator does not need a weight variable.
  • ora-02789 : Maximum number of files reached
  • ora-15156 : cluster in rolling upgrade from version [string] to [string]
  • ora-24295 : max key length (string) for sorted hash cluster exceeded
  • ora-08331 : Wait operation timed out
  • ora-01585 : error identifying backup file string
  • ora-38494 : column in the table alias and an attribute have matching names
  • ora-29961 : too many warnings occurred in the execution of ODCIIndex DDL routine
  • ora-24808 : streaming of lob data is not allowed when using lob buffering
  • ora-12547 : TNS:lost contact
  • ora-37012 : (XSACQUIRE_TIMEOUT) Object workspace object is locked by another user and the WAIT timed out.
  • ora-13759 : User "string" cannot remove reference "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.