1. log-in to Admin Server Console 2. In left pane of console, expand Environment and select Servers. 3. On the Summary of Servers page,select Managed Server instance i.e EMGC_OMS1 4. To enable tunneling of connections, On the Protocols > General tab: Check Enable tunneling. Click Save.
JVM memory settings: create or replace function getMaxMemorySize return number is language java name 'oracle.aurora.vm.OracleRuntime.getMaxMemorySize() returns long'; / create or replace function getMaxRunspaceSize return number is language java name 'oracle.aurora.vm.OracleRuntime.getMaxRunspaceSize() returns long'; / create or replace function getMaxSessionSize return number is language java name 'oracle.aurora.vm.OracleRuntime.getMaxSessionSize() returns long'; / SQL> select getMaxMemorySize from dual; SQL> select getMaxSessionSize from dual; SQL> select getMaxRunspaceSize from dual; JVM usage: create or replace function getJavaStackSize return number is language java name 'oracle.aurora.vm.OracleRuntime.getJavaStackSize() returns long'; / create or replace function getJavaPoolSize return number is language java name 'oracle.aurora.vm.OracleRuntime.getJavaPoolSize() returns long'; / SQL> select getJavaStackS...
I found this bug several times using version 10.2.0.2 until 10.2.0.5, i used to solve it just by changing the optimizer mode to RULE in the RMAN session. Solution: sql "alter session set optimizer_mode=RULE"; Execute your RMAN backup scripts.
set linesize 300 set serveroutput on size 100000 set feedback off set timing on set term off set head off spool rebuild.log begin dbms_output.enable('9999999'); for rIndex in (select s.owner,s.segment_name,sum(s.bytes/1024/1024) from dba_segments s , dba_indexes i where s.segment_type = 'INDEX' and s.segment_name = i.index_name and s.owner = i.owner and i.index_type = 'NORMAL' and s.owner not in ('SYS','SYSTEM','SYSMAN','SYSAUX','APPLSYS') group by s.owner,s.segment_name having sum(bytes/1024/1024) > 100) loop execute immediate 'analyze index '||rIndex.owner||'.'||rIndex.segment_name||' validate structure'; end loop; dbms_output.put_line('--- Reorganizando os indices ---'); for rRebuild in(SELECT name, height, lf_rows, owner FROM INDEX_STATS st, dba_indexes di where st.name = di.index_name) loop execute immediate 'alter index '||rRebuild.owner||'....
Error: SQL> startup ORA-27102: out of memory SVR4 Error: 22: Invalid argument And the alert log shows something similar to the following. WARNING: EINVAL creating segment of size 0x000000002a000000 fix shm parameters in /etc/system or equivalent Solution: For example, a sample /etc/system entry setting SHMMAX = 6GB. set shmsys:shminfo_shmmax=6442450944 (6*1024*1024*1024) set semsys:seminfo_semmni=1024 set semsys:seminfo_semmsl=1024 set shmsys:shminfo_shmmni=100 (see note id: 169706.1 for solaris requeriments ) Database started with above settings ok, and missing project settings in this case were the following. 1. # projadd -c "Oracle" 'user.oracle' 2. # projmod -s -K "project.max-shm-memory=(privileged,6GB,deny)" 'user.oracle'
Drop datapump external tables: select OWNER,OBJECT_NAME,OBJECT_TYPE, status, to_char(CREATED,'dd-mon-yyyy hh24:mi:ss') created ,to_char(LAST_DDL_TIME , 'dd-mon-yyyy hh24:mi:ss') last_ddl_time from dba_objects where object_name like 'ET$%' / select owner, TABLE_NAME, DEFAULT_DIRECTORY_NAME, ACCESS_TYPE from dba_external_tables order by 1,2 / Doc. ID: 1274653.1