ORA-01159: file is not from same database as previous files - wrong database id

SQL> @E:\yoonus.sql
ORACLE instance started.
Total System Global Area 1358954496 bytes
Fixed Size                  2077456 bytes
Variable Size             687869168 bytes
Database Buffers          654311424 bytes
Redo Buffers               14696448 bytes
CREATE CONTROLFILE REUSE DATABASE "GEP" NORESETLOGS  ARCHIVELOG
*
ERROR at line 1:
ORA-01503: CREATE CONTROLFILE failed
ORA-01159: file is not from same database as previous files - wrong database id
ORA-01517: log member: 'E:\ORACLE\GEP\ORIGLOGA\LOG_G11M1.DBF'


SOLUTION:

Change the control file value from :( if you are using newly installed system's log file change as follows)

CREATE CONTROLFILE REUSE DATABASE "GEP" NORESETLOGS  ARCHIVELOG  to

CREATE CONTROLFILE REUSE SET DATABASE "GEP" RESETLOGS  ARCHIVELOG


SQL> @E:\yoonus.sql
ORACLE instance started.
Total System Global Area 1358954496 bytes
Fixed Size                  2077456 bytes
Variable Size             687869168 bytes
Database Buffers          654311424 bytes
Redo Buffers               14696448 bytes
Control file created.

SQL>

Thanks
Yoonus

ORA-01166: file number 255 is larger than MAXDATAFILES (254)

SQL> @E:\yoonus.sql
ORACLE instance started.
Total System Global Area 1358954496 bytes
Fixed Size                  2077456 bytes
Variable Size             687869168 bytes
Database Buffers          654311424 bytes
Redo Buffers               14696448 bytes
CREATE CONTROLFILE REUSE DATABASE "GEP" NORESETLOGS  ARCHIVELOG
*
ERROR at line 1:
ORA-01503: CREATE CONTROLFILE failed
ORA-01166: file number 255 is larger than MAXDATAFILES (254)
ORA-01110: data file 255: 'X:\GEPDB1010\SR3.DATA226'

Solution:

Edit the control file and increase the number of MAXDATAFILE VALUES



STARTUP NOMOUNT
CREATE CONTROLFILE REUSE DATABASE "GEP" NORESETLOGS  ARCHIVELOG
    MAXLOGFILES 255
    MAXLOGMEMBERS 3
    MAXDATAFILES 254 increase to more than your data files count
    MAXINSTANCES 50
    MAXLOGHISTORY 1168
LOGFILE
  GROUP 1 (
    'E:\ORACLE\GEP\ORIGLOGA\LOG_G11M1.DBF',
    'E:\ORACLE\GEP\MIRRLOGA\LOG_G11M2.DBF'
  ) SIZE 50M,
  GROUP 2 (
    'E:\ORACLE\GEP\ORIGLOGB\LOG_G12M1.DBF',
    'E:\ORACLE\GEP\MIRRLOGB\LOG_G12M2.DBF'

Thanks
Yoonus

Unlimit the failed login attempts in ORACLE, SAPSR3: ORA-28000: the account is locked

ALTER PROFILE DEFAULT LIMIT FAILED_LOGIN_ATTEMPTS UNLIMITED;

Symptom

You cannot log on to the Oracle database and the program returns the message:

ORA-28000: the account is locked

Other Terms

Reason and Prerequisites

ORA-28000 is usually triggered because someone has previously attempted to log on several times using an incorrect password, which causes the logon to fail and returns ORA-01017. The number of allowed logon attempts is defined by the resource FAILED_LOGIN_ATTEMPTS in the profile. You can determine the current value of this parameter using the following query:

SELECT LIMIT FROM DBA_PROFILES
WHERE
  PROFILE = 'DEFAULT' AND
  RESOURCE_NAME = 'FAILED_LOGIN_ATTEMPTS';

Until Oracle 10.1, this parameter had the default value UNLIMITED, so that no ORA-28000 messages would normally occur. As of Oracle 10.2, this standard value has been set to 10.

A further option in the case of a locked user is an explicit lock as follows:

ALTER USER <username> ACCOUNT LOCK;

Solution

To prevent ORA-28000 errors, and avoid similar problems in future, be aware of the following:

• If you use Oracle 9i or earlier, do not manually restrict the authorizations of the default profile (also refer to Note 700548 (16)).

• If FAILED_LOGIN_ATTEMPTS is not set to UNLIMITED, you can adjust it as follows:
  
  ALTER PROFILE DEFAULT LIMIT FAILED_LOGIN_ATTEMPTS UNLIMITED;

           This is also possible for Oracle 10. 1 and earlier and Oracle 10.2 and later.

• If a user is already locked, you can unlock it as follows:
  
  ALTER USER <username> ACCOUNT UNLOCK;

           If the ORA-28000 error occurred due to a large number of failed logon attempts, you must check why these logon attempts were unsuccessful and returned the ORA-01017 error. The cause is often an incorrect configuration of the OPS$ mechanism. In this case, refer to Note 400241.

  Thanks Yoonus

ORA-01130: database file version 11.2.0.4.0 incompatible with ORACLE version 11.2.0.0.0

ORA-01503: CREATE CONTROLFILE failed
ORA-01130: database file version 11.2.0.4.0 incompatible with ORACLE version 11.2.0.0.0

Solution:
 
Check the compatible parameter values in  INISID.ora and SPFlLESID.ora
 
Adjust the value and restart the database

R3load.exe -i SAPSPROT.cmd -dbcodepage 4103 -l SAPSPROT.log -stop_on_error Loading of 'SAPSSEXC' import package is interrupted with R3load error.

Error 1

0

IMPORT_ABAP Error. Loading of 'SAPSSEXC' import package is interrupted with R3load error.

Error 2

2EETW169 no connect possible: "connect failed with DBLI_RC_LOAD_LIB_FAILED."

Error 3
SAP Java Server VM (build 6.1.068 24.55-b13, Jun 22 2014 00:31:35 - 61_REL - optU - windows amd64 - 6 - bas2:220276 (mixed mode))
Import Monitor jobs: running 1, waiting 8, completed 19, failed 0, total 28.
Import Monitor jobs: running 2, waiting 7, completed 19, failed 0, total 28.
Import Monitor jobs: running 3, waiting 6, completed 19, failed 0, total 28.
Import Monitor jobs: running 4, waiting 5, completed 19, failed 0, total 28.
Import Monitor jobs: running 5, waiting 4, completed 19, failed 0, total 28.
Import Monitor jobs: running 6, waiting 3, completed 19, failed 0, total 28.
Import Monitor jobs: running 7, waiting 2, completed 19, failed 0, total 28.
Import Monitor jobs: running 8, waiting 1, completed 19, failed 0, total 28.
Loading of 'SAPSLOAD' import package: ERROR
Import Monitor jobs: running 7, waiting 1, completed 19, failed 1, total 28.
Loading of 'SAPSSRC' import package: ERROR
Import Monitor jobs: running 6, waiting 1, completed 19, failed 2, total 28.
Loading of 'SAPAPPL1' import package: ERROR
Import Monitor jobs: running 5, waiting 1, completed 19, failed 3, total 28.
Loading of 'SAPAPPL0' import package: ERROR
Import Monitor jobs: running 4, waiting 1, completed 19, failed 4, total 28.
Loading of 'SAPSSEXC' import package: ERROR
Import Monitor jobs: running 3, waiting 1, completed 19, failed 5, total 28.
Loading of 'SAPAPPL2' import package: ERROR
Import Monitor jobs: running 2, waiting 1, completed 19, failed 6, total 28.
Loading of 'SAPSDIC' import package: ERROR
Import Monitor jobs: running 1, waiting 1, completed 19, failed 7, total 28.
Loading of 'SAPSPROT' import package: ERROR
Import Monitor jobs: running 0, waiting 1, completed 19, failed 8, total 28.
================
Error 4
C:\usr\sap\GEP\SYS\exe\uc\NTAMD64\R3load.exe -ctf I C:\INST\SAP_-ECC6.FULL DUMP\Inst_Export\DATA_UNITS\EXPORT_11\DATA\SAPSSRC.STR C:\Program Files\sapinst_instdir\BS2008\ERP604\AS-ABAP\ORA\CENTRAL\DDLORA.TPL SAPSSRC.TSK ORA -l SAPSSRC.log
Error 4
C:\usr\sap\GEP\SYS\exe\uc\NTAMD64\R3load.exe: job completed
C:\usr\sap\GEP\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20180510121345
C:\usr\sap\GEP\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20180510121345
C:\usr\sap\GEP\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/720_REL/src/R3ld/R3load/R3ldmain.c#3 $ SAP
C:\usr\sap\GEP\SYS\exe\uc\NTAMD64\R3load.exe: version R7.20/V1.4 [UNICODE]
Compiled May  7 2010 03:19:51
C:\usr\sap\GEP\SYS\exe\uc\NTAMD64\R3load.exe -i SAPSSRC.cmd -dbcodepage 4103 -l SAPSSRC.log -stop_on_error
DbSl Trace: ORA-942 when accessing table SAPUSER

Error 6

TRACE      2018-05-14 12:39:45.313 [syxxcfile.cpp:85]
           CSyFileImpl::decideIfMoveCopyNode(const CopyMoveDestinationInfo & {m_nodeTypeForCombiCheck: ..., m_path: C:/Program Files/sapinst_instdir/BS2008/ERP604/AS-ABAP/ORA/CENTRAL/__instana_tmp.11.xml, m_realNodeType: 8}, ISyNode::CopyMoveMode_t 0x3, PSyNodeInt &) const 
           lib=syslib module=syslib
Target node does not exist and (mode & ISyNode::MISSING) ==> I will copy/move.

Loading of 'SAPSSEXC' import package is interrupted with R3load error.


Solution:

One:
execute r3loade.exe if throwing an error msvcr120.dll missing
to apply this download vcredist_x64 https://www.microsoft.com/en-us/download/details.aspx?id=40784

Two:

Check below environment values are set properly

dba_ora_schema
dbms_type
ORACLE_HOME
SAPDATA_HOME
ORACLE_SID
RSEC_SSFS_DATAPATH
RSEC_SSFS_KEYPATH

Three:

check the BRTOOL version which support the database version and instant client versions.

Most probably issue is SAPSR3 user is getting locked while trying to importabap . Avoid this  Unlock the user


SQL> select username ,account_status  from dba_users;

SAPSR3                                                                         
LOCKED(TIMED)  

SQL> alter user sapsr3 account unlock;

The execute the below comment to avoid  locking again:


ALTER PROFILE DEFAULT LIMIT FAILED_LOGIN_ATTEMPTS UNLIMITED;

Refer the snote: 951167 - ORA-28000: the account is locked

Symptom

You cannot log on to the Oracle database and the program returns the message:

ORA-28000: the account is locked

Other Terms

Reason and Prerequisites

ORA-28000 is usually triggered because someone has previously attempted to log on several times using an incorrect password, which causes the logon to fail and returns ORA-01017. The number of allowed logon attempts is defined by the resource FAILED_LOGIN_ATTEMPTS in the profile. You can determine the current value of this parameter using the following query:

SELECT LIMIT FROM DBA_PROFILES
WHERE
  PROFILE = 'DEFAULT' AND
  RESOURCE_NAME = 'FAILED_LOGIN_ATTEMPTS';

Until Oracle 10.1, this parameter had the default value UNLIMITED, so that no ORA-28000 messages would normally occur. As of Oracle 10.2, this standard value has been set to 10.

A further option in the case of a locked user is an explicit lock as follows:

ALTER USER <username> ACCOUNT LOCK;

Solution

To prevent ORA-28000 errors, and avoid similar problems in future, be aware of the following:

• If you use Oracle 9i or earlier, do not manually restrict the authorizations of the default profile (also refer to Note 700548 (16)).

• If FAILED_LOGIN_ATTEMPTS is not set to UNLIMITED, you can adjust it as follows:
  
  ALTER PROFILE DEFAULT LIMIT FAILED_LOGIN_ATTEMPTS UNLIMITED;

           This is also possible for Oracle 10. 1 and earlier and Oracle 10.2 and later.

• If a user is already locked, you can unlock it as follows:
  
  ALTER USER <username> ACCOUNT UNLOCK;

           If the ORA-28000 error occurred due to a large number of failed logon attempts, you must check why these logon attempts were unsuccessful and returned the ORA-01017 error. The cause is often an incorrect configuration of the OPS$ mechanism. In this case, refer to Note 400241.

 
Thanks
Yoonus

--- dbs_ora_tnsname , TNS-03505: Failed to resolve name

C:\Users\SAPadm>r3trans -x
This is r3trans version 6.24 (release 722 - 24.03.17 - 20:17:03).
unicode enabled version
R3trans=>sapparam(1c): No Profile used.
R3trans=>sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
2EETW169 no connect possible: "DBMS = ORACLE                           --- dbs_ora_tnsname = 'EEP'"
r3trans finished (0012).

Solution:

Correct the  TNS file entry and SQLnet.ora file.

entry missing in TNSNAME.ora





C:\Users\SApadm>tnsping EEP
TNS Ping Utility for 64-bit Windows: Version 12.1.0.2.0 - Production on 09-MAY-2018 12:06:57
Copyright (c) 1997, 2014, Oracle.  All rights reserved.
Used parameter files:
C:\usr\sap\EEP\SYS\profile\oracle\sqlnet.ora
TNS-03505: Failed to resolve name






THANKS
yOONUS

brrestore from EMC Networker and DataDomain

BRRESTORE from Networker software: ORACLE DATABASE.

Scenario explaining how to restore using backup from EMC DD& Netwroker using BRrestore.  Database should be backed up using backnit tools from EMC. The backup should be completed successfully at the application level as well as database level. User can check the backup status using TXN db12 and verify the status.

Source system and target system should be the same database and patch level as well OS also. (recommended) try to keep the same drive as source system.

On the target machine EMC networker backup should be configure and backed up before restoring the source.

STEP1:

initSID.utl File must be created while configuring the backup to the target machine. Edit the  “initSID.utl” file and add the following parameter. Normally the file located in to % ORACLE_HOME% database folder

NSR_NWPATH = C:\Program Files\EMC NetWorker\nsr\bin\

NSR_DEVICE_INTERFACE=DATA_DOMAIN

NSR_RECOVER_POOL = GEP2018

client = eccsapgrp.TEST.local 

server = backupsrvr.TEST.local

debug_level=9

verbose=TRUE

#NSR_DPRINTF=TRUE

Above parameter details:

NSR_NWPATH= networker installed path in target machine

NSR_RECOVER_POOL = source system data backup pool

Client= sources system hostname  FQN if configured.

Server = networker backup server(media server)

Save the file after adding the parameter, in to same location.File should have read and write access to the ora_dba user and sapSIDadm user.

TOTAL FILE details below.

###########################################################################

#

# This is the <init>.utl file.

#

# This file contains settings for the NetWorker Module for SAP with

# Oracle (a.k.a. NMSAP).

#

# Note: Comments have a "#" in the first column.

#

###########################################################################

# Default Value: 8

# Valid Values: > 0 integer

# Number of simultaneous savesets/savestreams to send to server.

# Be sure your server and devices are configured to support at least

# as many streams.

#

# parallelism = 8

parallelism = 30

# Default Value: no

# Valid Values: no/yes

# Group saveset by file system

# If set to 'yes', savesets parameter will be ignored

#

# ss_group_by_fs = yes

ss_group_by_fs = FALSE

# Additional configuration options.

# These are optional fields.

#

NSR_NWPATH = C:\Program Files\EMC NetWorker\nsr\bin\

NSR_DEVICE_INTERFACE=DATA_DOMAIN

NSR_RECOVER_POOL = GEP2018

client = eccsapgrp.geepas.local

server = backupsrvr.geepas.local

debug_level=9

verbose=TRUE

#NSR_DPRINTF=TRUE

STEP 2:

Copy xxx.anf file to the %sapdata_home%\sapbackup. .anf file either located in to source system %sapdata_home%\sapbackup – folder or into the backup location where you backed up last backup.

Brrestore will perform the restore based on .anf file.

Once place the .anf file into the sapbackup folder open cmd with administrative right and run the below scrip:

You must edit the script based on the file location and .anf file name.

brrestore -p C:\oracle\GEP\102\database\initGEP.sap -d util_file -r C:\oracle\GEP\102\database\initGEP.utl -m full -b beybvnzl.anf -m full -m all=X:\restore -c force

Above script I am restoring all 6TB database data file in to the X: drive\restore folder. In this scenario all data file will be restored into the X:\restore folder without parent and subfolder. Once restore complete you can see the logs into the same sapbackup folder with file extension .rsb.


datadomain
=========================
ddboost show stats interval 2      =
=========================

Once all data file completely restored into the drive you need to restore archive logs from the backup location.

STEP3:

After that create control file using control file script.

STARTUP NOMOUNT

CREATE CONTROLFILE REUSE DATABASE "GEP" RESETLOGS  ARCHIVELOG

    MAXLOGFILES 255

    MAXLOGMEMBERS 3

    MAXDATAFILES 508

    MAXINSTANCES 50

    MAXLOGHISTORY 93484

LOGFILE

  GROUP 1 (

    'E:\ORACLE\GEP\ORIGLOGA\LOG_G11M1.DBF',

    'F:\ORACLE\GEP\MIRRLOGA\LOG_G11M2.DBF'

  ) SIZE 150M,

  GROUP 2 (

    'E:\ORACLE\GEP\ORIGLOGB\LOG_G12M1.DBF',

    'F:\ORACLE\GEP\MIRRLOGB\LOG_G12M2.DBF'

  ) SIZE 150M,

  GROUP 3 (

    'E:\ORACLE\GEP\ORIGLOGA\LOG_G13M1.DBF',

    'F:\ORACLE\GEP\MIRRLOGA\LOG_G13M2.DBF'

  ) SIZE 150M,

  GROUP 4 (

    'E:\ORACLE\GEP\ORIGLOGB\LOG_G14M1.DBF',

    'F:\ORACLE\GEP\MIRRLOGB\LOG_G14M2.DBF'

  ) SIZE 150M

-- STANDBY LOGFILE

DATAFILE

  'X:\restore\SYSTEM.DATA1',

  'X:\restore\UNDO.DATA1',

  'X:\restore\SYSAUX.DATA1',

  'X:\restore\SR3.DATA1',

  'X:\restore\SR3.DATA2',

  'X:\restore\SR3.DATA3'

CHARACTER SET UTF8

;

SQL> @h:\geP.sql
ORACLE instance started.
Total System Global Area 1.0452E+10 bytes
Fixed Size                  2094864 bytes
Variable Size            5268048112 bytes
Database Buffers         5167382528 bytes
Redo Buffers               14680064 bytes
Control file created.

SQL> alter database open;
alter database open
*
ERROR at line 1:
ORA-01589: must use RESETLOGS or NORESETLOGS option for database open

SQL> alter database open resetlogs;
alter database open resetlogs
*
ERROR at line 1:
ORA-01195: online backup of file 1 needs more recovery to be consistent
ORA-01110: data file 1: 'H:\GED\V\ORACLE\GED\SAPDATA1\SYSTEM_1\SYSTEM.DATA1'

SQL> recover database using backup controlfile;
ORA-00279: change 3368505684 generated at 03/11/2018 18:30:18 needed for thread
1
ORA-00289: suggestion : G:\ORACLE\GEP\ORAARCH\GEDARCH1_51014_713190785.DBF
ORA-00280: change 3368505684 for thread 1 is in sequence #51014

Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
G:\ORACLE\GEP\ORAARCH\GEDARCH1_51014_713190785.DBF
ORA-00279: change 3368506852 generated at 03/11/2018 18:38:41 needed for thread
1
ORA-00289: suggestion : G:\ORACLE\GEP\ORAARCH\GEDARCH1_51015_713190785.DBF
ORA-00280: change 3368506852 for thread 1 is in sequence #51015
ORA-00278: log file 'G:\ORACLE\GEP\ORAARCH\GEDARCH1_51014_713190785.DBF' no
longer needed for this recovery

Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
CANCEL
Media recovery cancelled.
SQL> recover database using backup controlfile until cancel;
ORA-00279: change 3368506852 generated at 03/11/2018 18:38:41 needed for thread
1
ORA-00289: suggestion : G:\ORACLE\GEP\ORAARCH\GEDARCH1_51015_713190785.DBF
ORA-00280: change 3368506852 for thread 1 is in sequence #51015

Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
CANCEL
Media recovery cancelled.
SQL> alter database open resetlogs;
Database altered.
SQL>

>.RSB file output

BR0401I BRRESTORE 7.20 (29)

BR0405I Start of file restore: reyebtvf.rsb 2018-04-02 17.16.43

BR0484I BRRESTORE log file: H:\oracle\GEP\sapbackup\reyebtvf.rsb

BR0101I Parameters

Name                           Value

oracle_sid                     GEP

oracle_home                    C:\oracle\GEP\102

oracle_profile                 C:\oracle\GEP\102\database\initGEP.ora

sapdata_home                   H:\oracle\GEP

sap_profile                    C:\oracle\GEP\102\database\initGEP.sap

recov_interval                 30

restore_mode                   ALL=X:\restore

backup_dev_type                util_file

util_par_file                  C:\oracle\GEP\102\database\initGEP.utl

system_info                    gepadm TESTGEP Windows 6.0 Build 6001 Service Pack 1 AMD64

oracle_info                    GEP 10.2.0.5.0

make_info                      NTAMD64 OCI_10201_SHARE Jan 16 2013

command_line                   brrestore -p C:\oracle\GEP\102\database\initGEP.sap -d util_file -r C:\oracle\GEP\102\database\initGEP.utl -m full -b beybvnzl.anf -m full -m all=X:\restore -c force

BR0460W Termination message not found in H:\oracle\GEP\sapbackup\beybvnzl.anf - log file incomplete (this is OK if the log file has been restored)

BR0456I Probably the database must be recovered due to restore from online backup

BR0280I BRRESTORE time stamp: 2018-04-02 17.16.43

BR0407I Restore of database: GEP

BR0408I BRRESTORE action ID: reyebtvf

BR0409I BRRESTORE function ID: rsb

BR0449I Restore mode: ALL=X:\restore

BR0419I Files will be restored from backup: beybvnzl.anf 2018-03-21 21.00.49

BR0416I 296 files found to restore, total size 5933436.313 MB

BR0421I Restore device type: util_file

BR0134I Unattended mode with 'force' active - no operator confirmation allowed

BR0280I BRRESTORE time stamp: 2018-04-02 17.16.43

BR0229I Calling backup utility with function 'restore'...

BR0278I Command output of 'C:\usr\sap\GEP\SYS\exe\uc\NTAMD64\backint.exe -u GEP -f restore -i H:\oracle\GEP\sapbackup\.reyebtvf.lst -t file -p C:\oracle\GEP\102\database\initGEP.utl -c':

BR0280I BRRESTORE time stamp: 2018-04-03 05.02.11

#FILE..... L:\ORACLE\GEP\SAPDATA3\SR3_246\SR3.DATA246  X:\restore\SR3.DATA246

#RESTORED. 1521651712

BR0280I BRRESTORE time stamp: 2018-04-03 05.02.11

BR0374I 96 of 96 files restored by backup utility

BR0230I Backup utility called successfully

BR0406I End of file restore: reyebtvf.rsb 2018-04-03 05.02.11

BR0280I BRRESTORE time stamp: 2018-04-03 05.02.11

BR0403I BRRESTORE completed successfully with warnings

ORA-27046: file size is not a multiple of logical block siz

Detail log:                    beybzphm.anf
BR0051I BRBACKUP 7.20 (42)
BR0055I Start of database backup: beybzphm.anf 2018-03-22 16.47.18
BR0484I BRBACKUP log file: C:\oracle\SOL\sapbackup\beybzphm.anf
BR0280I BRBACKUP time stamp: 2018-03-22 16.47.18
BR0301E SQL error -1565 at location BrInitOraCreate-5, SQL statement:
'/* BRBACKUP AT PROF_CONN */ CREATE PFILE = 'C:\oracle\SOL\11203\database\sapSOL.ora' FROM SPFILE = 'C:\oracle\SOL\11203\database\spfileSOL.ora''
ORA-01565: error in identifying file 'C:\oracle\SOL\11203\database\spfileSOL.ora'
ORA-27046: file size is not a multiple of logical block size
OSD-04012: file size mismatch (OS 5678)
BR0303E Determination of Oracle version failed
BR0056I End of database backup: beybzphm.anf 2018-03-22 16.47.18
BR0280I BRBACKUP time stamp: 2018-03-22 16.47.18
BR0054I BRBACKUP terminated with errors
BR0280I BRBACKUP time stamp: 2018-03-22 16.47.18
BR0291I BRARCHIVE will be started with options '+beybzphm.anf -U  -sd -d util_file -r C:\oracle\SOL\11203\database\tmp_6328.utl -p C:\oracle\SOL\11203\database\initSOL.sap -c for
BR0280I BRBACKUP time stamp: 2018-03-22 16.47.19
BR0292E Execution of BRARCHIVE finished with return code 3


Solution:


SQL> shut immediate;
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> create spfile from pfile;
File created.
SQL> startup
ORACLE instance started.
Total System Global Area 1369653248 bytes
Fixed Size                  2255024 bytes
Variable Size             687867728 bytes
Database Buffers          654311424 bytes
Redo Buffers               25219072 bytes
Database mounted.
Database opened.
SQL>

CLI recover from EMC networker media server

Test Scenario: GEPARCH1_1538190_819962162.DBF  missing File cannot find in DD by browsing NW client

Login to NW Media server:

CHECK THE MISSIGN FILE NAME  FROM DD  CMD blow
========================
C:\logs>mminfo -avot -q client=eccsapgrp.xxxx.local -r name,ssid,ssid(50),savetime,ssbrowse,ssretent,volume | findstr GEPARCH1_1538190_819962162.DBF

Check the Date n time

C:\logs>nsrinfo -X all -n all eccsapgrp.geepas.local | findstr GEPARCH1_1538190_819962162.DBF

output:

G:\oracle\GEP\oraarch\GEPARCH1_1538190_819962162.DBF, date=1520641855 3/10/2018 4:30:55 AM

C:\logs>mminfo -avot -q client=eccsapgrp.geepas.local -r name,ssid,ssid(50),savetime,ssbrowse,ssretent,volume,nsavetime | findstr 15206418

output:
backint:GEP                    1235429127 1235429127                                        3/10/2018 4/10/2018 4/10/2018 GEPONLINE2017.00

Recover particular file:GEPARCH1_1538190_819962162.DBF 

C:\logs>recover -d C:\logs -S 1235429127 G:\oracle\GEP\oraarch\GEPARCH1_1538190_819962162.DBF
Recovering a subset of 26 files within / into C:\logs
Recover start time: 3/17/2018 3:34:34 PM
Requesting 1 recover session(s) from server.
libDDBoost version: major: 3, minor: 0, patch: 1, engineering: 1, build: 459919
C:\logs\G\oracle\GEP\oraarch\GEPARCH1_1538190_819962162.DBF
C:\logs\G\oracle\GEP\oraarch\
C:\logs\G\oracle\GEP\
C:\logs\G\oracle\
C:\logs\G\
Received 5 matching file(s) from NSR server `backupsrvr.geepas.local'
Recover completion time: 3/17/2018 3:35:38 PM


Thanks
Yoonus

HETROGENEOUSE SAP/ORACLE ONLINE DATABASE RESTORE...

RESTORING ONLINE DATABASE backup  TO DIFFRENT SID . WITH ARCHIVE LOGS.

"This scenario, my source system sid is GED and target system sid is GEP"
 
eg: RESTORE GED DATABSE TO GEP SYSTEM
RESTORE ALL DATA FILE INTO  THE DRIVE ANY LOCATION AND CREATE CONTROL FILE SCRIPT AS YOU RESTORED THE FILE.
IF RESTORING TO DIFFRENT SID  CHANGE THE FOLLOWING VALUES IN PARAMETER
init(SID).ora{FILE:\DATABASE\}
log_archive_dest_1='LOCATION=G:\oracle\GEP\oraarch\GEDarch'  (orginal archive file name was 'GEParch' but I am restoring GED db sid , so it will prompt  the archvie file name starting with GEParch since your target system installed as GEP sid and path defined as GEParch)
If your data files numbers morethan 256 COUNT  please increase the number of  'db_files' IN [parameter ]


Control file creation scripts as follows:
=====================
STARTUP NOMOUNT
CREATE CONTROLFILE REUSE SET DATABASE "GEP" RESETLOGS  ARCHIVELOG
    MAXLOGFILES 255
    MAXLOGMEMBERS 3
    MAXDATAFILES 254
    MAXINSTANCES 50
    MAXLOGHISTORY 5842
LOGFILE
  GROUP 1 (
    'H:\GED\V\oracle\GED\ORIGLOGA\LOG_G11M1.DBF',
    'H:\GED\V\oracle\GED\MIRRLOGA\LOG_G11M2.DBF'
  ) SIZE 50M,
  GROUP 2 (
    'H:\GED\V\oracle\GED\ORIGLOGB\LOG_G12M1.DBF',
    'H:\GED\V\oracle\GED\MIRRLOGB\LOG_G12M2.DBF'
  ) SIZE 50M,
  GROUP 3 (
    'H:\GED\V\oracle\GED\ORIGLOGA\LOG_G13M1.DBF',
    'H:\GED\V\oracle\GED\MIRRLOGA\LOG_G13M2.DBF'
  ) SIZE 50M,
  GROUP 4 (
    'H:\GED\V\oracle\GED\ORIGLOGB\LOG_G14M1.DBF',
    'H:\GED\V\oracle\GED\MIRRLOGB\LOG_G14M2.DBF'
  ) SIZE 50M
-- STANDBY LOGFILE
DATAFILE
  'H:\GED\V\oracle\GED\SAPDATA1\SYSTEM_1\SYSTEM.DATA1',
  'H:\GED\V\oracle\GED\SAPDATA1\UNDO_1\UNDO.DATA1',
  'H:\GED\V\oracle\GED\SAPDATA1\SYSAUX_1\SYSAUX.DATA1',
  'H:\GED\V\oracle\GED\SAPDATA2\SR3_1\SR3.DATA1',
  'H:\GED\V\oracle\GED\SAPDATA2\SR3_2\SR3.DATA2',
  'H:\GED\V\oracle\GED\SAPDATA2\SR3_3\SR3.DATA3',
  'H:\GED\V\oracle\GED\SAPDATA2\SR3_4\SR3.DATA4',
  'H:\GED\V\oracle\GED\SAPDATA2\SR3_5\SR3.DATA5',
  'H:\GED\V\oracle\GED\SAPDATA2\SR3_6\SR3.DATA6',
  'H:\GED\V\oracle\GED\SAPDATA2\SR3_7\SR3.DATA7',
  'H:\GED\V\oracle\GED\SAPDATA2\SR3_8\SR3.DATA8',
  'H:\GED\V\oracle\GED\SAPDATA2\SR3_9\SR3.DATA9',
  'H:\GED\V\oracle\GED\SAPDATA2\SR3_10\SR3.DATA10',
  'H:\GED\V\oracle\GED\SAPDATA2\SR3_11\SR3.DATA11',
  'H:\GED\V\oracle\GED\SAPDATA2\SR3_12\SR3.DATA12',
  'H:\GED\V\oracle\GED\SAPDATA2\SR3_13\SR3.DATA13',
  'H:\GED\V\oracle\GED\SAPDATA2\SR3_14\SR3.DATA14',
  'H:\GED\V\oracle\GED\SAPDATA2\SR3_15\SR3.DATA15',
  'H:\GED\V\oracle\GED\SAPDATA2\SR3_16\SR3.DATA16',
  'H:\GED\V\oracle\GED\SAPDATA3\SR3701_1\SR3701.DATA1',
  'H:\GED\V\oracle\GED\SAPDATA3\SR3701_2\SR3701.DATA2',
  'H:\GED\V\oracle\GED\SAPDATA3\SR3701_3\SR3701.DATA3',
  'H:\GED\V\oracle\GED\SAPDATA3\SR3701_4\SR3701.DATA4',
  'H:\GED\V\oracle\GED\SAPDATA3\SR3701_5\SR3701.DATA5',
  'H:\GED\V\oracle\GED\SAPDATA3\SR3701_6\SR3701.DATA6',
  'H:\GED\V\oracle\GED\SAPDATA3\SR3701_7\SR3701.DATA7',
  'H:\GED\V\oracle\GED\SAPDATA3\SR3701_8\SR3701.DATA8',
  'H:\GED\V\oracle\GED\SAPDATA3\SR3701_9\SR3701.DATA9',
  'H:\GED\V\oracle\GED\SAPDATA3\SR3701_10\SR3701.DATA10',
  'H:\GED\V\oracle\GED\SAPDATA3\SR3701_11\SR3701.DATA11',
  'H:\GED\V\oracle\GED\SAPDATA3\SR3701_12\SR3701.DATA12',
  'H:\GED\V\oracle\GED\SAPDATA3\SR3701_13\SR3701.DATA13',
  'H:\GED\V\oracle\GED\SAPDATA3\SR3701_14\SR3701.DATA14',
  'H:\GED\V\oracle\GED\SAPDATA4\SR3USR_1\SR3USR.DATA1',
  'H:\GED\V\oracle\GED\SAPDATA4\SR3701X_1\SR3701X.DATA1',
  'H:\GED\V\oracle\GED\SAPDATA4\SR3701X_2\SR3701X.DATA2',
  'H:\GED\V\oracle\GED\SAPDATA4\SR3701X_3\SR3701X.DATA3',
  'H:\GED\V\oracle\GED\SAPDATA4\SR3701X_4\SR3701X.DATA4',
  'H:\GED\V\oracle\GED\SAPDATA4\SR3701X_5\SR3701X.DATA5',
  'H:\GED\V\oracle\GED\SAPDATA1\SYSAUX_2\SYSAUX.DATA2',
  'H:\GED\V\oracle\GED\SAPDATA1\SYSTEM_2\SYSTEM.DATA2',
  'H:\GED\V\oracle\GED\SAPDATA4\SR3701X_6\SR3701X.DATA6',
  'H:\GED\V\oracle\GED\SAPDATA4\SR3701X_7\SR3701X.DATA7',
  'H:\GED\V\oracle\GED\SAPDATA2\SR3_17\SR3.DATA17',
  'H:\GED\V\oracle\GED\SAPDATA2\SR3_18\SR3.DATA18',
  'H:\GED\V\oracle\GED\SAPDATA2\SR3_19\SR3.DATA19',
  'H:\GED\V\oracle\GED\SAPDATA4\SR3701X_8\SR3701X.DATA8',
  'H:\GED\V\oracle\GED\SAPDATA2\SR3_20\SR3.DATA20',
  'H:\GED\V\oracle\GED\SAPDATA2\SR3_21\SR3.DATA21',
  'H:\GED\V\oracle\GED\SAPDATA2\SR3_22\SR3.DATA22',
  'H:\GED\V\oracle\GED\SAPDATA2\SR3_23\SR3.DATA23',
  'H:\GED\V\oracle\GED\SAPDATA2\SR3_24\SR3.DATA24',
  'H:\GED\V\oracle\GED\SAPDATA2\SR3_25\SR3.DATA25',
  'H:\GED\V\oracle\GED\SAPDATA2\SR3_26\SR3.DATA26',
  'H:\GED\V\oracle\GED\SAPDATA2\SR3_27\SR3.DATA27',
  'H:\GED\V\oracle\GED\SAPDATA2\SR3_28\SR3.DATA28',
  'H:\GED\V\oracle\GED\SAPDATA2\SR3_29\SR3.DATA29',
  'H:\GED\V\oracle\GED\SAPDATA2\SR3_30\SR3.DATA30',
  'H:\GED\V\oracle\GED\SAPDATA2\SR3_31\SR3.DATA31',
  'H:\GED\V\oracle\GED\SAPDATA4\SR3701X_9\SR3701X.DATA9',
  'H:\GED\V\oracle\GED\SAPDATA2\SR3_32\SR3.DATA32'
CHARACTER SET UTF8;
================================================================
restore using below commands
SQL> @h:\ged.sql
ORACLE instance started.
Total System Global Area 1.0452E+10 bytes
Fixed Size                  2094864 bytes
Variable Size            5268048112 bytes
Database Buffers         5167382528 bytes
Redo Buffers               14680064 bytes
Control file created.
SQL> alter database open;
alter database open
*
ERROR at line 1:
ORA-01589: must use RESETLOGS or NORESETLOGS option for database open

SQL> alter database open resetlogs;
alter database open resetlogs
*
ERROR at line 1:
ORA-01195: online backup of file 1 needs more recovery to be consistent
ORA-01110: data file 1: 'H:\GED\V\ORACLE\GED\SAPDATA1\SYSTEM_1\SYSTEM.DATA1'

SQL> recover database using backup controlfile;
ORA-00279: change 3368505684 generated at 03/11/2018 18:30:18 needed for thread
1
ORA-00289: suggestion : G:\ORACLE\GEP\ORAARCH\GEDARCH1_51014_713190785.DBF
ORA-00280: change 3368505684 for thread 1 is in sequence #51014

Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
G:\ORACLE\GEP\ORAARCH\GEDARCH1_51014_713190785.DBF
ORA-00279: change 3368506852 generated at 03/11/2018 18:38:41 needed for thread
1
ORA-00289: suggestion : G:\ORACLE\GEP\ORAARCH\GEDARCH1_51015_713190785.DBF
ORA-00280: change 3368506852 for thread 1 is in sequence #51015
ORA-00278: log file 'G:\ORACLE\GEP\ORAARCH\GEDARCH1_51014_713190785.DBF' no
longer needed for this recovery

Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
CANCEL
Media recovery cancelled.
SQL> recover database using backup controlfile until cancel;
ORA-00279: change 3368506852 generated at 03/11/2018 18:38:41 needed for thread
1
ORA-00289: suggestion : G:\ORACLE\GEP\ORAARCH\GEDARCH1_51015_713190785.DBF
ORA-00280: change 3368506852 for thread 1 is in sequence #51015

Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
CANCEL
Media recovery cancelled.
SQL> alter database open resetlogs;
Database altered.
SQL>

For update SAP user Login  Follow the below link:

https://wrongcodes.blogspot.com/2015/07/ops-user-id-creation-after-backup.html




THANKS
YOONUS CHANGOTH
https://www.linkedin.com/in/yoonusabdulla/