C:\Users\Hp>sqlplus SYSTEM as SYSDBA
SQL*Plus: Release 11.2.0.1.0 Production on Wed Aug 3 12:28:32 2016
Copyright (c) 1982, 2010, Oracle. All rights reserved.
Enter password:
Connected to an idle instance.
SQL> startup
ORA-00119: invalid specification for system parameter LOCAL_LISTENER
ORA-00132: syntax error or unresolved network name 'LISTENER_ORCL'
SQL> create pfile from spfile;
File created.
**************************
Now open the PFILE (INIT%ORACLE_SID%.ORA) from %ORACLE_HOME%\database
Search for string local_listener='LISTENER_ORCL' and remove it and save the file.
**************************
SQL> startup nomount pfile='C:\app\Hp\product\11.2.0\dbhome_1\database\INITorcl.ORA'
ORACLE instance started.
Total System Global Area 1686925312 bytes
Fixed Size 2176368 bytes
Variable Size 1291848336 bytes
Database Buffers 385875968 bytes
Redo Buffers 7024640 bytes
SQL> create spfile from pfile;
File created.
SQL> startup
ORA-01081: cannot start already-running ORACLE - shut it down first
SQL> shutdown
ORA-01507: database not mounted
ORACLE instance shut down.
SQL> startup
ORACLE instance started.
Total System Global Area 1686925312 bytes
Fixed Size 2176368 bytes
Variable Size 1291848336 bytes
Database Buffers 385875968 bytes
Redo Buffers 7024640 bytes
Database mounted.
Database opened.
also make sure that your lsnrctl work fine or not if not then please check !!
NOW, when you do these steps we nee now to change character set
STEPS TO FOLLOW TO CHANGE THE DATABASE CHARACTER SET FROM UTF8 TO AL32
SQL>STARTUP RESTRICT
SQL>ALTER DATABASE CHARACTER SET INTERNAL_USE AL32UTF8;
SQL>ALTER DATABASE CHARACTER SET AL32UTF8;
SQL>SHUT IMMEDIATE OR SHUTDOWN
SQL>STARTUP
"MAKE SURE AND CHECK THAT WE CANNOT CHANGE CHARACTER SET FROM HIGHER TO LOWER VERSION
Choosing an Oracle Database Character Set
Oracle uses the database character set for:
- Data stored in SQL
CHAR
datatypes (CHAR
, VARCHAR2
, CLOB
, and LONG)
- Identifiers such as table names, column names, and PL/SQL variables
- Entering and storing SQL and PL/SQL source code
The character encoding scheme used by the database is defined as part of the CREATE
DATABASE
statement. All SQL CHAR
datatype columns (CHAR
, CLOB
, VARCHAR2
, and LONG)
, including columns in the data dictionary, have their data stored in the database character set. In addition, the choice of database character set determines which characters can name objects in the database. SQL NCHAR
datatype columns (NCHAR
, NCLOB
, and NVARCHAR2)
use the national character set.
Note:
CLOB data is encoded as UCS-2 if the database character set is multibyte. If the database character set is single-byte, then CLOB data is stored in the database character set.
|
After the database is created, you cannot change the character sets, with some exceptions, without re-creating the database.
Consider the following questions when you choose an Oracle character set for the database:
- What languages does the database need to support now?
- What languages will the database need to support in the future?
- Is the character set available on the operating system?
- What character sets are used on clients?
- How well does the application handle the character set?
- What are the performance implications of the character set?
- What are the restrictions associated with the character set?
DONT FORGET TO COMMENT !!
Comments
Post a Comment