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 : 20-08-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-00307 : requested INSTANCE_NUMBER out of range, maximum is string
  • ora-34181 : (MXCHGDCL21) workspace object is not a partitioned VARIABLE.
  • ora-15010 : name is already used by an existing ASM disk
  • ora-36714 : (XSMXALLOC03) TARGETLOG variable workspace object must have the same data type as TARGET variable workspace object.
  • ora-12673 : Dedicated server: context not saved
  • ora-14169 : invalid ALTER TABLE MODIFY SUBPARTITION option
  • ora-08444 : syntax error in JUSTIFIED clause in mask options
  • ora-07473 : snclrd: read error when trying to read sgadef.dbf file.
  • ora-32124 : Illegal attribute passed
  • ora-16045 : circular archive log destination dependency chain
  • ora-39173 : Encrypted data has been stored unencrypted in dump file set.
  • ora-03119 : two-task detected inconsistent datatype specification
  • ora-27006 : sbtremove returned error
  • ora-25426 : remote instance does not support shared dblinks
  • ora-06914 : CMX: unexepected event during start of oracle
  • ora-25401 : can not continue fetches
  • ora-37152 : MDX query error: (string)
  • ora-09362 : Windows 3.1 Two-Task driver unable to deallocate context area
  • ora-31609 : error loading file "string" from file system directory "string"
  • ora-04090 : 'string' specifies same table, event and trigger time as 'string'
  • ora-31693 : Table data object string failed to load/unload and is being skipped due to error: string
  • ora-28140 : Invalid column specified
  • ora-15075 : disk(s) are not visible cluster-wide
  • ora-39022 : Database version string is not supported.
  • ora-39036 : invalid metadata filter name string
  • ora-08238 : smsfre: cannot detach from SGA
  • ora-30130 : invalid parameter key type received
  • ora-38733 : Physical size string less than needed string.
  • ora-26056 : Requested direct path operation on a view is not supported.
  • ora-38861 : flashback recovery stopped before reaching recovery target
  • 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.