cancel
Showing results for 
Search instead for 
Did you mean: 

Urgent: DBrefresh error 354 while creating control file, oracle9i, SAP R3

Former Member
0 Kudos

Hi experts,

I have created trace file in Source system and moved the same to target system and edited and then while executing the trace file to create control file the following eeror is coming

my trace file is like this. . .

..............................................

STARTUP NOMOUNT

CREATE CONTROLFILE SET DATABASE "P47" RESETLOGS ARCHIVELOG

-- SET STANDBY TO MAXIMIZE PERFORMANCE

MAXLOGFILES 255

MAXLOGMEMBERS 3

MAXDATAFILES 336

MAXINSTANCES 50

MAXLOGHISTORY 8168

...

...

..

'/oracle/P47/sapdata9/btabd_63/btabd.data63',

'/oracle/P47/sapdata9/stabi_27/stabi.data27',

'/oracle/P47/sapdata9/btabi_122/btabi.data122',

'/oracle/P47/sapdata9/stabd_28/stabd.data28',

'/oracle/P47/sapdata9/btabi_123/btabi.data123',

'/oracle/P47/sapdata9/btabd_64/btabd.data64',

'/oracle/P47/sapdata9/btabi_124/btabi.data124'

CHARACTER SET WE8DEC

......................................................

i run command like this:

SQL> @/oracle/P47/saptrace/usertrace/control.sql

ORACLE instance started.

Total System Global Area 1249618992 bytes

Fixed Size 732208 bytes

Variable Size 788529152 bytes

Database Buffers 459022446 bytes

Redo Buffers 1335296 bytes

<b>354</b>

when I press 'enter' again SQL prompt is comming

Please help

rgds

Accepted Solutions (0)

Answers (1)

Answers (1)

markus_doehr2
Active Contributor
0 Kudos

I can´t see any error.... I just see "354"...

Do you see anything in your Oracle alert log?

--

Markus

Former Member
0 Kudos

Hi markus,

thanks for reply . .

control files are not created. . . .

alertSID logs shows as follows

..............................

orap47> tail -f alert_P47.log

ARCH shutting down

Thu Dec 13 13:01:51 2007

ARC0: Archival stopped

Thu Dec 13 13:01:51 2007

ARC1: Archival stopped

Thu Dec 13 13:01:54 2007

ARCH: Archiving is disabled

Shutting down archive processes

Archiving is disabled

Archive process shutdown avoided: 0 active

<b>When @/oracle/saptrace/usertrace/control.sql command given in sepearate SQL window</b>

Thu Dec 13 13:03:37 2007

Starting ORACLE instance (normal)

Disable cache advisory with old cache parameters

Thu Dec 13 13:03:37 2007

WARNING: EINVAL creating segment of size 0x000000004b800000

fix shm parameters in /etc/system or equivalent

LICENSE_MAX_SESSION = 0

LICENSE_SESSIONS_WARNING = 0

SCN scheme 3

LICENSE_MAX_USERS = 0

SYS auditing is disabled

Starting up ORACLE RDBMS Version: 9.2.0.4.0.

System parameters with non-default values:

processes = 80

sessions = 96

timed_statistics = TRUE

shared_pool_size = 704643072

enqueue_resources = 8000

control_files = /oracle/P47/sapdata1/cntrl/cntrlP47.dbf, /oracle/P47/sapdata2/cntrl/cntrlP47.dbf, /oracle/P47/sapdata3/cntrl/cntrlP47.dbf

db_block_buffers = 56033

db_block_checksum = FALSE

db_block_size = 8192

compatible = 9.2.0

log_archive_start = TRUE

log_archive_dest = /oracle/P47/saparch/P47arch

log_buffer = 1048576

log_checkpoint_interval = 0

db_files = 354

db_file_multiblock_read_count= 8

log_checkpoints_to_alert = TRUE

control_file_record_keep_time= 30

dml_locks = 2500

row_locking = always

replication_dependency_tracking= FALSE

transactions_per_rollback_segment= 20

rollback_segments = PRS_0, PRS_1, PRS_10, PRS_11, PRS_12, PRS_13, PRS_14, PRS_2, PRS_3, PRS_4, PRS_5, PRS_6, PRS_7, PRS_8, PRS_9

transaction_auditing = FALSE

remote_os_authent = TRUE

db_domain = world

parallel_max_servers = 20

hash_join_enabled = FALSE

background_dump_dest = /oracle/P47/saptrace/background

user_dump_dest = /oracle/P47/saptrace/usertrace

core_dump_dest = /oracle/P47/saptrace/background

optimizer_features_enable= 9.2.0

sort_area_size = 2097152

sort_area_retained_size = 0

db_name = P47

open_cursors = 800

optimizer_mode = choose

btree_bitmap_plans = FALSE

pushjoin_predicate = FALSE

optimizer_index_cost_adj = 10

newinitial_join_orders = FALSE

optimpeek_user_binds = FALSE

PMON started with pid=2

DBW0 started with pid=3

LGWR started with pid=4

CKPT started with pid=5

SMON started with pid=6

RECO started with pid=7

Thu Dec 13 13:03:39 2007

ARCH: STARTING ARCH PROCESSES

ARC0 started with pid=8

ARC0: Archival started

ARC1 started with pid=9

Thu Dec 13 13:03:39 2007

ARCH: STARTING ARCH PROCESSES COMPLETE

Thu Dec 13 13:03:39 2007

ARC0: Thread not mounted

Thu Dec 13 13:03:39 2007

ARC1: Archival started

ARC1: Thread not mounted

.............................................................................

rgds

markus_doehr2
Active Contributor
0 Kudos

Are you on Solaris? If yes, your IPC settings are not correct:

WARNING: EINVAL creating segment of size 0x000000004b800000

fix shm parameters in /etc/system or equivalent

Apart from that I can´t see any error.

--

Markus

Former Member
0 Kudos

markus!

Yes it is solaris.....

how to set the IPC settings. . .

Please guide me. .

rgds

markus_doehr2
Active Contributor
0 Kudos

Depending on your Solaris version:

395438 Parameter settings for Solaris 9 and below

724713 parameter settings for Solaris 10

I also suggest to update your database version, 9.2.0.4 is already VERY old.

--

Markus

Former Member
0 Kudos

Thanks Markus. . .

I check ed the parameters in /etc/system compared with source and target systems. Both are identical.

oracle patch levels are different:

Source: 9.2.0.7

target: 9.2.0.4

os is solaris 9 spark

rgds

markus_doehr2
Active Contributor
0 Kudos

The target version must have at least the source version of the database.

I suggest to Install patchset 9.2.0.7 on the target system and try to create the database again with your control.sql.

--

Markus

Former Member
0 Kudos

Hi Markus!

My problem solved!

In vi editor by mistake i deleted semi colon also. So 354 is line where attn to be paid.

it was like this brfore:

CHARACTER SET WE8DEC

~

~

I changed to:

CHARACTER SET WE8DEC

;

~

then control files created . . .btw line 354 was CHARACTER SET WE8DEC

rgds

markus_doehr2
Active Contributor
0 Kudos

Good to hear!

I would though path the target system up to 9.2.0.7. If you copy the database from that version, the internal Oracle dictionary has a different version than the software on the filesystem which may lead to all sorts of strange errors.

--

Markus