Conversion between archive mode and non-archive Mode

1. Check whether the database is in archive mode.

SQL> archive log list;

 

2. Transition from non-archive mode to archive Mode

C: \ Documents ents and Settings \ Administrator> cd \
C: \> lsnrctl status

C: \> sqlplus/nolog
SQL> conn sys/system @ ora10g as sysdba
SQL> shutdown immediate;
SQL> startup mount;
ORA-12514: TNS: The Listener currently cannot identify the Service requested in the connection Descriptor
SQL> exit
C: \> lsnrctl status
C: \> slqplus/nolog
SQL> conn sys/system @ ora10g as sysdba;
ERROR:
ORA-12514: TNS: The Listener currently cannot identify the Service requested in the connection Descriptor
SQL> set display verbose
SP2-0158: Unknown SET Option "display"
SQL> exit
C: \> set display verbose
The environment variable display is not defined.
C: \> lsnrctl
LSNRCTL for 32-bit Windows: Version 10.2.0.1.0-Production on-2008
1: 37

LSNRCTL> set display verbose
The service display mode is VERBOSE.
LSNRCTL> service
LSNRCTL> start
TNS-01106: a listener started with the name LISTENER
LSNRCTL> reload
Connecting to (DESCRIPTION = (ADDRESS = (PROTOCOL = IPC) (KEY = EXTPROC1 )))
Command executed successfully
LSNRCTL> exit
C: \> sqlplus/nolog
SQL> conn sys/system as sysdba
Already connected to the idle routine.
SQL> startup mount;
The ORACLE routine has been started.
SQL> alter database archivelog;
The database has been changed.
SQL> alter database open;
The database has been changed.
SQL> archive log list;
Database Log mode archiving Mode
Enable automatic archiving
Archiving end point USE_DB_RECOVERY_FILE_DEST
Oldest online log sequence 131
Next archive log sequence 133
Current Log sequence 133
SQL>

3. Modify the JAVA_POOL_SIZE parameter.

Answer1:
First, check whether your database is started with spfile or pfile.
SQL> show parameter spfile;
-----------------------------------------------------------------------------
Spfile string % ORACLE_HOME %/DATABASE/SPFILE %
ORACLE_SID %. ORA
SQL>
It indicates that spfile is enabled.
You can modify JAVA_POOL_SIZE and SHARED_POOL_SIZE dynamically;
SQL> alter system set shared_pool_size = 50331648 scope = both
System altered.
SQL>
Similarly, JAVA_POOL_SIZE
SQL> alter system set Java _ pool_size = 50331648 scope = both
System altered.
SQL>
If pfile is used for startup, you need to close the database.
Modify the size of JAVA_POOL_SIZE and SHARED_POOL_SIZE in init % ORACLE_SID %. ORA.
You can open the file in the text editor to modify the preceding two parameters.
I use abort To disable it here. Please use it with caution as needed.
SQL> shutdown abort
ORACLE instance shut down.
SQL> create spfile from pfile;
File created.
SQL> startup
ORACLE instance started.
Total System Global Area 152115804 bytes
Fixed Size 453212 bytes
Variable Size 125829120 bytes
Database Buffers 25165824 bytes
Redo Buffers 667648 bytes
Database mounted.
Database opened.
SQL>
Now the modification is complete.
Note: If the database is started using spfile, it can be dynamically modified without restarting.
If pfile is used, restart it.

Answer2:
I started it with pfile.
I want to close the database and modify it.
SQL> shutdown immediate
Edit init. ora in notepad.
I would like to ask if JAVA_POOL_SIZE should be changed to a smaller value after the database is upgraded?
What is the proper value for JAVA_POOL_SIZE under normal conditions?
Answer3:
In 9.2, the default JAVA_POOL_SIZE is 16 M.
Generally, you do not need to modify JAVA_POOL_SIZE unless a large number of java programs are developed in oracle.