update : 29-04-2017

DBA Script : wm_enable_versioning.sql

-- | FILE : wm_enable_versioning.sql |
-- +----------------------------------------------------------------------------+
-- | |
-- | |
-- | www.high-oracle.com |
-- |----------------------------------------------------------------------------|
-- | www.high-oracle.com |
-- |----------------------------------------------------------------------------|
-- | DATABASE : Oracle |
-- | FILE : wm_enable_versioning.sql |
-- | CLASS : Workspace Manager |
-- | PURPOSE : Prompt the user for an owner and table name. This table will be |
-- | "version enabled" for use with Workspace Manager. This is often |
-- | the first step in using Oracle's Workspace Manager feature. |
-- | This script creates the necessary structures to enable the |
-- | specified table to support multiple versions of rows. The |
-- | length of a table name must not exceed 25 characters. The name |
-- | is not case sensitive. The table that is being version-enabled |
-- | must have a primary key defined. Only the owner of a table can |
-- | enable versioning on the table. Tables that are version-enabled |
-- | and users that own version-enabled tables cannot be deleted. |
-- | You must first disable versioning on the relevant table or |
-- | tables. Tables owned by SYS cannot be version-enabled. An |
-- | exception is raised if the table is already version-enabled. |
-- | NOTE : As with any code, ensure to test this script in a development |
-- | environment before attempting to run it in production. |
-- +----------------------------------------------------------------------------+
SET TERMOUT OFF;
COLUMN current_instance NEW_VALUE current_instance NOPRINT;
SELECT rpad(sys_context('USERENV', 'INSTANCE_NAME'), 17) current_instance
FROM dual;
SET TERMOUT ON;
PROMPT
PROMPT +------------------------------------------------------------------------+
PROMPT | Report : Enable Table Versioning for Current Workspace |
PROMPT | Instance : ¤t_instance |
PROMPT +------------------------------------------------------------------------+
SET ECHO OFF
SET FEEDBACK 6
SET HEADING ON
SET LINESIZE 180
SET PAGESIZE 50000
SET TERMOUT ON
SET TIMING OFF
SET TRIMOUT ON
SET TRIMSPOOL ON
SET VERIFY OFF
COLUMN getworkspace FORMAT a50 HEADING "Current Workspace"
COLUMN ver_tables FORMAT a50 HEADING "All Current Versioned Tables"
SELECT dbms_wm.getworkspace FROM dual;
SELECT
owner || '.' || table_name AS ver_tables
FROM
wmsys.wm$versioned_tables
UNION ALL
SELECT
'No versioned tables found'
FROM
dual
WHERE NOT EXISTS ( SELECT owner, table_name
FROM wmsys.wm$versioned_tables)
ORDER BY 1;
PROMPT
ACCEPT wm_ev_owner CHAR PROMPT 'Enter table owner : '
ACCEPT wm_ev_table CHAR PROMPT 'Enter table name : '
PROMPT
DEFINE wm_ev_table_name = &wm_ev_owner..&wm_ev_table
BEGIN
dbms_wm.enableversioning('&wm_ev_table_name');
END;
/
SELECT
owner || '.' || table_name AS ver_tables
FROM
wmsys.wm$versioned_tables
UNION ALL
SELECT
'No versioned tables found'
FROM
dual
WHERE NOT EXISTS ( SELECT owner, table_name
FROM wmsys.wm$versioned_tables)
ORDER BY 1;

End Script

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.