GLOBALIZATION SUPPORT
Choosing a Character Set
---------------------------------
When computer systems process characters, they use numeric codes instead of the graphical representation of the character. For example, when the database stores the letter A, it actually stores a numeric code that is interpreted by software as that letter. Read on to know more about Globalization Support.
ForMoreDetails
NLS Data Dictionary Views
----------------------------
Applications can check the session, instance, and database NLS parameters by
querying the following data dictionary views:
NLS_SESSION_PARAMETERS shows the NLS parameters and their values for the
session that is querying the view. It does not show information about the character
set.
NLS_INSTANCE_PARAMETERS shows the current NLS instance parameters that
have been explicitly set and the values of the NLS instance parameters.
NLS_DATABASE_PARAMETERS shows the values of the NLS parameters for the
database. The values are stored in the database.
--------------------------------------------------------
NLS Dynamic Performance Views
V$NLS_VALID_VALUES lists values for the following NLS parameters
NLS_LANGUAGE, NLS_SORT, NLS_TERRITORY, NLS_CHARACTERSET
V$NLS_PARAMETERS shows current values of the following NLS parameters:
NLS_CALENDAR, NLS_CHARACTERSET, NLS_CURRENCY, NLS_DATE_FORMAT,
NLS_DATE_LANGUAGE, NLS_ISO_CURRENCY, NLS_LANGUAGE, NLS_NUMERIC_
CHARACTERS, NLS_SORT, NLS_TERRITORY, NLS_NCHAR_CHARACTERSET, NLS_COMP, NLS_LENGTH_SEMANTICS, NLS_NCHAR_CONV_EXP, NLS_TIMESTAMP_FORMAT, NLS_TIMESTAMP_TZ_FORMAT, NLS_TIME_FORMAT, NLS_TIME_TZ_FORMAT
--------
Nov 12, 2010
Nov 11, 2010
Nov 8, 2010
Oracle Golden Gate
For Real-time data integration.High performing enterprises need real-time data access across heterogeneous systems for improved business intelligence.Enables zero-downtime migration and upgrades for mission critical Oracle Applications.Supports the vast majority of databases and operating systems.
Continuous Availability
-----------------------
• Faster recovery
• Minimal data loss
Fast, Accurate Decision
----------------------------
• Real-time
• Operational business intelligence
Value Across Multiple Solutions
-------------------------------
• Rapid deployment
• Single technology highly flexible
-------
Continuous Availability
-----------------------
• Faster recovery
• Minimal data loss
Fast, Accurate Decision
----------------------------
• Real-time
• Operational business intelligence
Value Across Multiple Solutions
-------------------------------
• Rapid deployment
• Single technology highly flexible
-------
Oct 29, 2010
To get only numeric values
To retrieve only numeric values from both numeric& character value
In 10 g
Select regexp_replace(regexp_replace('5RTYDDB','([[:punct:]])'),'([[:alpha:]])')
from dual t
In 9i
select replace('BBd3',TRANSLATE('BBd3', ' +-.0123456789', ' '),'') from dual
------------
In 10 g
Select regexp_replace(regexp_replace('5RTYDDB','([[:punct:]])'),'([[:alpha:]])')
from dual t
In 9i
select replace('BBd3',TRANSLATE('BBd3', ' +-.0123456789', ' '),'') from dual
------------
Oct 19, 2010
DBMS_WM.CompressWorkspace
DBMS_WM.Compress Workspace
If you version enabled the tables with DBMS_WM.EnableVersioning ('TABLE_NAME', 'VIEW_WO_OVERWRITE') API THEN your Oracle Workspace database WILL GET SLOW WHEN SO MANY DATA COMES ; use DBMS_WM.CompressWorkspace API TO MAKE IT FASTER; There is a scenario to check whether your Workspace is getting slow or Workspace database is to be Compressed or not ,execute this workspace API
DBMS_WM.SetDiffVersions('LIVE',wksp2) . and then pick a version enabled table having highest record count , issue command select count(*) from tablename_diff ; if it takes more than a minute to GET RESULT THEN YOU CAN MAKE SURE THAT YOU NEED TO COMPRESS YOUR WORKSPACE ;here u want to use the statement (1) , using statement (2) will not give better result because your table is version enabled with DBMS_WM.EnableVersioning ('TABLE_NAME', 'VIEW_WO_OVERWRITE') .
(1) exec DBMS_WM.CompressWorkspace('LIVE',compress_view_wo_overwrite => true);
(2) exec DBMS_WM.CompressWorkspace('LIVE')
VIEW_WO_OVERWRITE: The without overwrite (WO_OVERWRITE) option. A view named_HIST is created to contain history information, and it will show all modifications to the same version of the table. A history of modifications to the version is maintained; that is, subsequent changes to a row in the same version do not overwrite earlier changes.
compress_view_wo_overwrite A Boolean value (TRUE or FALSE).
TRUE causes history information between the affected savepoints to be deleted even if VIEW_WO_OVERWRITE was specified when versioning was enabled.
FALSE causes history information (between the affected savepoints) for a table not to be deleted if VIEW_WO_OVERWRITE was specified when versioning was enabled. (If VIEW_WO_OVERWRITE was not specified for a table, history information for the table is deleted regardless of the parameter value.) FALSE is assumed if the procedure format without this parameter is used.
Advantage
------------
1 Run-time performance for Workspace Manager operations is improved.
2 Less disk storage is used for Workspace Manager structures
If you version enabled the tables with DBMS_WM.EnableVersioning ('TABLE_NAME', 'VIEW_WO_OVERWRITE') API THEN your Oracle Workspace database WILL GET SLOW WHEN SO MANY DATA COMES ; use DBMS_WM.CompressWorkspace API TO MAKE IT FASTER; There is a scenario to check whether your Workspace is getting slow or Workspace database is to be Compressed or not ,execute this workspace API
DBMS_WM.SetDiffVersions('LIVE',wksp2) . and then pick a version enabled table having highest record count , issue command select count(*) from tablename_diff ; if it takes more than a minute to GET RESULT THEN YOU CAN MAKE SURE THAT YOU NEED TO COMPRESS YOUR WORKSPACE ;here u want to use the statement (1) , using statement (2) will not give better result because your table is version enabled with DBMS_WM.EnableVersioning ('TABLE_NAME', 'VIEW_WO_OVERWRITE') .
(1) exec DBMS_WM.CompressWorkspace('LIVE',compress_view_wo_overwrite => true);
(2) exec DBMS_WM.CompressWorkspace('LIVE')
VIEW_WO_OVERWRITE: The without overwrite (WO_OVERWRITE) option. A view named
compress_view_wo_overwrite A Boolean value (TRUE or FALSE).
TRUE causes history information between the affected savepoints to be deleted even if VIEW_WO_OVERWRITE was specified when versioning was enabled.
FALSE causes history information (between the affected savepoints) for a table not to be deleted if VIEW_WO_OVERWRITE was specified when versioning was enabled. (If VIEW_WO_OVERWRITE was not specified for a table, history information for the table is deleted regardless of the parameter value.) FALSE is assumed if the procedure format without this parameter is used.
Advantage
------------
1 Run-time performance for Workspace Manager operations is improved.
2 Less disk storage is used for Workspace Manager structures
Subscribe to:
Posts (Atom)