Delta error in PRD
Hi
We are extracting the deltas into ODS from R/3. There was an error in extraction and activation into ODS didnt take place. The error is of invalid characteristics. The status is RED in monitor where as in data target--> manage the request is in green color but not active. I clicked on activate button and tried to activate manually but it was not getting activated.
I did the following steps.
1. In monitor screen, i converted the request into RED status.
2. In data target, i deleted the request.
3. Went to PSA, Manually changed the record and saved it. AFter changing the record the status in PSA is RED.
4. From PSA i scheduled the upload into data target immedialtely.
5. AFter scheduling, i could see the green request in datatarget with reporting icon. But the strange thing is in monitor screen the status [total] is in RED status and Technical is in GREEN status.
Q1. Now will delta takes place in next schedule, if tis in RED status?
REgards
Rak
Hi
ABY: If i repeat the delta, i will get the same error. Now i know what the error is and fixed up in PSA. We informed client and told them that it should not be done again.
Singh: After editing the record in PSA. i scheduled the upload and upload went fine in ODS. As i mentioned in the earlier thread.
In monitor screen the status is in RED where as in data target the request is in green status.
The editied record in PSA is In GREEN status,,,whereas total status is in RED.
What heppens if i turn that status into GREEN now? As i got the delta records into datatarget now.
Regards
Rak
Similar Messages
-
Table Maintenance Generator giving Error in PRD.
Hello Experts,
I am receiving below error in PRD for a Table Maintenance generator for Z-Table. PFA Screen Shot.
My Query is that though the information icon narrates to goto T-code SE54 & Re-generate TMG for the specified Function group. Which Option should 1 select after i had selection the option for Edit Function group->Re-generate group specific program.
The info icon in the first pic says to do the following.
Choose 'Edit Function Group' in the transaction SE54, enter the function group name 'ZOTMTRDPROFITSEG' and choose 'Regenerate Group-Specific Programs'. Choose 'Refresh Structure-Spec. Data Declarations' in the next selection window.
Would like to add a point that this Function grp also contains TMG for other tables as well, will it impact other TMG's.
Best Regards
Priyesh Shahregenerate the TM object via SE11 - Table maintenance.
normally should do the trick.
However, keep the func groups & tables 1:1 saves a lot of this kind of problem.
Don't mix them up i.e. more than 1 tab maint for a func group - never ending hassle you will get!!!
go into Expert mode and regen it again. Remove the maint from this func group and create new func group for the table. -
Delta error in GE-Function Module
Hi ,
my GE-delta is based on UDATE ( chenged date) from CDHDR table.
i created datasource in RS02 and i defined delta based in UDATE with upper limit 1 day and lower limit is '0'..
i created FM based on RSAX_BIW_GEDATA_SIMPLE.
for full load it working fine.
i put some extra code for delta.
it is not take any records...
i dont know much ABAP.
plz tell me where is wrong in my code for delta..
code ...
FUNCTION ZXBWMM_INV_POT_ID.
""Local Interface:
*" IMPORTING
*" VALUE(I_REQUNR) TYPE SRSC_S_IF_SIMPLE-REQUNR
*" VALUE(I_DSOURCE) TYPE SRSC_S_IF_SIMPLE-DSOURCE OPTIONAL
*" VALUE(I_MAXSIZE) TYPE SRSC_S_IF_SIMPLE-MAXSIZE OPTIONAL
*" VALUE(I_INITFLAG) TYPE SRSC_S_IF_SIMPLE-INITFLAG OPTIONAL
*" VALUE(I_READ_ONLY) TYPE SRSC_S_IF_SIMPLE-READONLY OPTIONAL
*" VALUE(I_REMOTE_CALL) TYPE SBIWA_FLAG DEFAULT SBIWA_C_FLAG_OFF
*" TABLES
*" I_T_SELECT TYPE SRSC_S_IF_SIMPLE-T_SELECT OPTIONAL
*" I_T_FIELDS TYPE SRSC_S_IF_SIMPLE-T_FIELDS OPTIONAL
*" E_T_DATA STRUCTURE ZVSAIPID OPTIONAL
*" EXCEPTIONS
*" NO_MORE_DATA
*" ERROR_PASSED_TO_MESS_HANDLER
Example: DataSource for table SFLIGHT
TABLES: SFLIGHT.
TABLES: EBAN , CDPOS , CDHDR , ZVSAPR.
TYPES : BEGIN OF TY_OBJDATE ,
OBJECTID TYPE CDHDR-OBJECTID,
VALUE_NEW TYPE CDPOS-VALUE_NEW,
VALUE_OLD TYPE CDPOS-VALUE_OLD,
UDATE TYPE CDHDR-UDATE,
MINBE TYPE MARC-MINBE,
BSTMA TYPE MARC-BSTMA,
WERKS TYPE MARC-WERKS,
VERPR TYPE MBEW-VERPR,
STPRS TYPE MBEW-STPRS,
LBKUM TYPE MBEW-LBKUM,
BUDAT TYPE MKPF-BUDAT,
MBLNR TYPE MSEG-MBLNR,
MENGE TYPE MSEG-MENGE,
DMBTR TYPE MSEG-DMBTR,
END OF TY_OBJDATE.
data : int_cdhdr type table of cdhdr with header line,
int_cdpos type table of cdpos with HEADER LINE,
INT_OBJDATE TYPE TABLE OF TY_OBJDATE WITH HEADER LINE.
int_marc type table of marc with header line.
*DATA: int_pr1 TYPE TABLE OF ZVSAIPID WITH HEADER LINE.
DATA : BEGIN OF INT_MATNR OCCURS 10,
MAtnr like mara-matnr,
end of int_matnr.
DATA : BEGIN OF INT_MARC OCCURS 10,
matnr like marc-matnr,
MINBE like marC-mINBE,
BSTMA LIKE Marc-bstma,
WERKS LIKE MARC-WERKS,
end of int_marc.
DATA : BEGIN OF INT_MBEW OCCURS 10,
MATNR LIKE MBEW-MATNR,
VERPR LIKE MBEW-VERPR,
STPRS LIKE MBEW-STPRS,
LBKUM LIKE MBEW-LBKUM,
end of int_MBEW.
DATA : BEGIN OF INT_MKPF OCCURS 10,
MBLNR LIKE MKPF-MBLNR,
BUDAT LIKE MKPF-BUDAT,
END OF INT_MKPF.
DATA : BEGIN OF INT_MSEG OCCURS 10,
MATNR LIKE MSEG-MATNR,
MBLNR LIKE MSEG-MBLNR,
MENGE LIKE MSEG-MENGE,
DMBTR LIKE MSEG-DMBTR,
END OF INT_MSEG.
Auxiliary Selection criteria structure
DATA: L_S_SELECT TYPE SRSC_S_SELECT.
Maximum number of lines for DB table
STATICS: S_S_IF TYPE SRSC_S_IF_SIMPLE,
counter
S_COUNTER_DATAPAKID LIKE SY-TABIX,
cursor
S_CURSOR TYPE CURSOR.
Select ranges
RANGES: L_R_CARRID FOR SFLIGHT-CARRID,
L_R_CONNID FOR SFLIGHT-CONNID.
RANGES : ra_OBJECTID FOR E_T_DATA-OBJECTID.
RA_UDATE FOR E_T_DATA-UDATE.
Initialization mode (first call by SAPI) or data transfer mode
(following calls) ?
IF I_INITFLAG = SBIWA_C_FLAG_ON.
IF NOT G_FLAG_INTERFACE_INITIALIZED IS INITIAL.
IF 1 = 2. MESSAGE E008(R3). ENDIF.
LOG_WRITE 'E' "message type
'R3' "message class
'008' "message number
' ' "message variable 1
' '. "message variable 2
RAISE ERROR_PASSED_TO_MESS_HANDLER.
ENDIF.
Initialization: check input parameters
buffer input parameters
prepare data selection
Check DataSource validity
CASE I_DSOURCE.
WHEN 'ZOI_MM_INVENTORY_IPID'.
WHEN OTHERS.
IF 1 = 2. MESSAGE E009(R3). ENDIF.
this is a typical log call. Please write every error message like this
LOG_WRITE 'E' "message type
'R3' "message class
'009' "message number
I_DSOURCE "message variable 1
' '. "message variable 2
RAISE ERROR_PASSED_TO_MESS_HANDLER.
ENDCASE.
Check for supported update mode
CASE I_UPDMODE.
WHEN 'F'.
WHEN 'D'.
WHEN 'R'.
WHEN OTHERS.
IF 1 = 2. MESSAGE E011(R3). ENDIF.
LOG_WRITE 'E' "message type
'R3' "message class
'011' "message number
I_UPDMODE "message variable 1
' '. "message variable 2
RAISE ERROR_PASSED_TO_MESS_HANDLER.
ENDCASE.
READ TABLE I_T_SELECT INTO L_S_SELECT
WITH KEY FIELDNM = 'UDATE'.
APPEND LINES OF I_T_SELECT TO S_S_IF-T_SELECT.
Fill parameter buffer for data extraction calls
S_S_IF-REQUNR = I_REQUNR.
S_S_IF-DSOURCE = I_DSOURCE.
S_S_IF-MAXSIZE = I_MAXSIZE.
G_S_INTERFACE-INITFLAG = I_INITFLAG.
G_S_INTERFACE-UPDMODE = I_UPDMODE.
G_S_INTERFACE-DATAPAKID = I_DATAPAKID.
G_FLAG_INTERFACE_INITIALIZED = SBIWA_C_FLAG_ON.
Fill field list table for an optimized select statement
(in case that there is no 1:1 relation between InfoSource fields
and database table fields this may be far from beeing trivial)
APPEND LINES OF I_T_FIELDS TO S_S_IF-T_FIELDS.
ELSE. "Initialization mode or data extraction ?
Data transfer: First Call OPEN CURSOR + FETCH
Following Calls FETCH only
First data package -> OPEN CURSOR
LOOP AT S_S_IF-T_SELECT INTO L_S_SELECT
WHERE FIELDNM = 'UDATE'.
ENDLOOP
IF S_COUNTER_DATAPAKID = 0.
Fill range tables BW will only pass down simple selection criteria
of the type SIGN = 'I' and OPTION = 'EQ' or OPTION = 'BT'.
LOOP AT S_S_IF-T_SELECT INTO L_S_SELECT WHERE FIELDNM = 'CARRID'.
MOVE-CORRESPONDING L_S_SELECT TO L_R_CARRID.
APPEND L_R_CARRID.
ENDLOOP.
LOOP AT S_S_IF-T_SELECT INTO L_S_SELECT WHERE FIELDNM = 'CONNID'.
MOVE-CORRESPONDING L_S_SELECT TO L_R_CONNID.
APPEND L_R_CONNID.
ENDLOOP.
Determine number of database records to be read per FETCH statement
from input parameter I_MAXSIZE. If there is a one to one relation
between DataSource table lines and database entries, this is trivial.
In other cases, it may be impossible and some estimated value has to
be determined.
OPEN CURSOR WITH HOLD S_CURSOR FOR
SELECT (S_S_IF-T_FIELDS) FROM SFLIGHT
WHERE CARRID IN L_R_CARRID AND
CONNID IN L_R_CONNID.
IF L_S_SELECT-LOW = '' AND L_S_SELECT-HIGH = ''. "FULL or INIT
OPEN CURSOR WITH HOLD S_CURSOR FOR
select * from cdhdr where OBJECTCLAS = 'MATERIAL' AND TCODE = 'MM02'.
ELSE. "DELTA
OPEN CURSOR WITH HOLD G_CURSOR FOR
select * from cdhdr where OBJECTCLAS = 'MATERIAL'
AND TCODE = 'MM02'
AND UDATE >= L_S_SELECT-LOW
AND UDATE <= L_S_SELECT-HIGH.
ENDIF.
ENDIF.
ENDIF.
"First data package ?
FETCH NEXT CURSOR S_CURSOR
APPENDING TABLE int_cdhdr
PACKAGE SIZE S_S_IF-MAXSIZE.
into table int_cdhdr
IF SY-SUBRC <> 0.
CLOSE CURSOR S_CURSOR.
RAISE NO_MORE_DATA.
ENDIF.
SELECT * FROM CDPOS INTO TABLE INT_CDPOS
FOR ALL ENTRIES IN INT_CDHDR
WHERE OBJECTID = INT_CDHDR-OBJECTID
AND TABNAME = 'MARC'
AND ( FNAME = 'BSTMA' OR FNAME = 'MINBE' ).
LOOP AT int_cdpos.
int_matnr-matnr = int_cdpos-objectid.
APPEND int_matnr.
ENDLOOP.
SELECT matnr MINBE BSTMA WERKS FROM MARC INTO TABLE INT_marc
FOR ALL ENTRIES IN int_matnr
WHERE MATNR = INT_matnr-matnr.
SELECT matnr VERPR STPRS LBKUM FROM MBEW INTO TABLE INT_MBEW
FOR ALL ENTRIES IN int_matnr
WHERE MATNR = INT_matnr-matnr.
SELECT matnr MBLNR MENGE DMBTR FROM MSEG INTO TABLE INT_MSEG
FOR ALL ENTRIES IN int_matnr
WHERE MATNR = INT_matnr-matnr.
LOOP AT int_MSEG.
int_MKPF-MBLNR = int_MSEG-MBLNR.
APPEND int_MKPF.
ENDLOOP.
SELECT MBLNR BUDAT FROM MKPF INTO TABLE INT_MKPF
FOR ALL ENTRIES IN int_MKPF
WHERE MBLNR = INT_MKPF-MBLNR.
*BREAK-POINT.
LOOP AT INT_CDPOS.
READ TABLE INT_CDHDR WITH KEY OBJECTID = INT_CDPOS-OBJECTID .
IF SY-SUBRC = 0.
INT_OBJDATE-OBJECTID = INT_CDPOS-OBJECTID.
INT_OBJDATE-VALUE_NEW = INT_CDPOS-VALUE_NEW.
INT_OBJDATE-VALUE_OLD = INT_CDPOS-VALUE_OLD.
INT_OBJDATE-UDATE = INT_CDHDR-UDATE.
READ TABLE INT_MARC WITH KEY MATNR = INT_CDPOS-OBJECTID .
IF SY-SUBRC = 0.
INT_OBJDATE-MINBE = INT_MARC-MINBE.
INT_OBJDATE-BSTMA = INT_MARC-BSTMA.
INT_OBJDATE-WERKS = INT_MARC-WERKS.
ENDIF.
READ TABLE INT_MBEW WITH KEY MATNR = INT_CDPOS-OBJECTID .
IF SY-SUBRC = 0.
INT_OBJDATE-VERPR = INT_MBEW-VERPR.
INT_OBJDATE-STPRS = INT_MBEW-STPRS.
INT_OBJDATE-LBKUM = INT_MBEW-LBKUM.
ENDIF.
READ TABLE INT_MSEG WITH KEY MATNR = INT_CDPOS-OBJECTID .
IF SY-SUBRC = 0.
INT_OBJDATE-MBLNR = INT_MSEG-MBLNR.
INT_OBJDATE-MENGE = INT_MSEG-MENGE.
INT_OBJDATE-DMBTR = INT_MSEG-DMBTR.
ENDIF.
READ TABLE INT_MKPF WITH KEY MBLNR = INT_MSEG-MBLNR .
IF SY-SUBRC = 0.
INT_OBJDATE-MBLNR = INT_MKPF-MBLNR.
INT_OBJDATE-BUDAT = INT_MKPF-BUDAT.
ENDIF.
APPEND INT_OBJDATE.
ENDIF.
ENDLOOP.
*SELECT * FROM EBAN
INTO CORRESPONDING FIELDS OF TABLE INT_PR1
FOR ALL ENTRIES IN INT_OBJDATE
WHERE BAnfn = int_objdate-objectid.
*ZZPRREL
LOOP AT INT_OBJDATE.
E_T_DATA-OBJECTID = INT_OBJDATE-OBJECTID.
E_T_DATA-UDATE = INT_OBJDATE-UDATE.
E_T_DATA-VALUE_NEW = INT_OBJDATE-VALUE_NEW.
E_T_DATA-VALUE_OLD = INT_OBJDATE-VALUE_OLD.
E_T_DATA-MINBE = INT_OBJDATE-MINBE.
E_T_DATA-BSTMA = INT_OBJDATE-BSTMA.
E_T_DATA-WERKS = INT_OBJDATE-WERKS.
E_T_DATA-VERPR = INT_OBJDATE-VERPR.
E_T_DATA-STPRS = INT_OBJDATE-STPRS.
E_T_DATA-LBKUM = INT_OBJDATE-LBKUM.
E_T_DATA-MBLNR = INT_OBJDATE-MBLNR.
E_T_DATA-MENGE = INT_OBJDATE-MENGE.
E_T_DATA-DMBTR = INT_OBJDATE-DMBTR.
E_T_DATA-BUDAT = INT_OBJDATE-BUDAT.
APPEND E_T_DATA.
CLEAR E_T_DATA.
ENDLOOP.
Fetch records into interface table.
named E_T_'Name of extract structure'.
S_COUNTER_DATAPAKID = S_COUNTER_DATAPAKID + 1.
ENDIF. "Initialization mode or data extraction ?
ENDFUNCTION.
i assign points....
Regards,
PSR.Hi ,
i am not find any sollution for this..
any body help me for this problum...
i assign points..
Regards,
PSR -
Hi All,
Please help me for the below backup log error.Backup was not comleted successfully.
Detail log: bdyjmnib.and
BR0051I BRBACKUP 7.00 (18)
BR0055I Start of database backup: bdyjmnib.and 2008-07-17 00.00.45
BR0477I Oracle pfile D:\oracle\PRD\102\database\initPRD.ora created from spfile D:\oracle\PRD\102\database\spfilePRD.ora
BR0280I BRBACKUP time stamp: 2008-07-17 00.00.47
BR0319I Control file copy created: D:\oracle\PRD\sapbackup\CNTRLPRD.DBF 21905408
BR0101I Parameters
Name Value
oracle_sid PRD
oracle_home D:\oracle\PRD\102
oracle_profile D:\oracle\PRD\102\database\initPRD.ora
sapdata_home D:\oracle\PRD
sap_profile D:\oracle\PRD\102\database\initPRD.sap
backup_mode ALL
backup_type online_cons
backup_dev_type disk
backup_root_dir F:\PRDBACKUP
compress yes
compress_cmd D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\mkszip -c $ > $
uncompress_cmd D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\uncompress -c $ > $
exec_parallel 0
system_info SAPServicePRD PRDSRV Windows 5.2 Build 3790 Service Pack 1 AMD64
oracle_info PRD 10.2.0.2.0 8192 5824 48559249 PRDSRV UTF8 UTF8
sap_info 700 SAPSR3 PRD TEMPLICENSE R3_ORA INITIAL
make_info NTAMD64 OCI_10201_SHARE Oct 26 2006
command_line brbackup -p initPRD.sap -d disk -t online_cons -m all -k yes -w -e 0 -l E -u system/********
BR0116I ARCHIVE LOG LIST before backup for database instance PRD
Parameter Value
Database log mode Archive Mode
Automatic archival Enabled
Archive destination E:\oracle\PRD\oraarch\PRDarch
Archive format ARC%S_%R.%T
Oldest online log sequence 5821
Next log sequence to archive 5824
Current log sequence 5824 SCN: 48559249
Database block size 8192 Thread: 1
Current system change number 48575196 ResetId: 644265653
BR0118I Tablespaces and data files
Tablespace TS-Status F-Status File Size Id. Device Link Type MaxSize IncrSize BlkSize
PSAPSR3 ONLINE* ONLINE+ D:\ORACLE\PRD\SAPDATA1\SR3_1\SR3.DATA1 2097160192 4 3 NOLINK FILE 10485760000 20971520 8192
PSAPSR3 ONLINE* ONLINE+ D:\ORACLE\PRD\SAPDATA1\SR3_2\SR3.DATA2 2097160192 5 3 NOLINK FILE 10485760000 20971520 8192
PSAPSR3 ONLINE* ONLINE+ D:\ORACLE\PRD\SAPDATA1\SR3_3\SR3.DATA3 2097160192 6 3 NOLINK FILE 10485760000 20971520 8192
PSAPSR3 ONLINE* ONLINE+ D:\ORACLE\PRD\SAPDATA1\SR3_4\SR3.DATA4 2097160192 7 3 NOLINK FILE 10485760000 20971520 8192
PSAPSR3 ONLINE* ONLINE+ D:\ORACLE\PRD\SAPDATA1\SR3_5\SR3.DATA5 2097160192 8 3 NOLINK FILE 10485760000 20971520 8192
PSAPSR3 ONLINE* ONLINE+ D:\ORACLE\PRD\SAPDATA2\SR3_10\SR3.DATA10 2160074752 13 3 NOLINK FILE 10485760000 20971520 8192
PSAPSR3 ONLINE* ONLINE+ D:\ORACLE\PRD\SAPDATA2\SR3_6\SR3.DATA6 2097160192 9 3 NOLINK FILE 10485760000 20971520 8192
PSAPSR3 ONLINE* ONLINE+ D:\ORACLE\PRD\SAPDATA2\SR3_7\SR3.DATA7 2097160192 10 3 NOLINK FILE 10485760000 20971520 8192
PSAPSR3 ONLINE* ONLINE+ D:\ORACLE\PRD\SAPDATA2\SR3_8\SR3.DATA8 2097160192 11 3 NOLINK FILE 10485760000 20971520 8192
PSAPSR3 ONLINE* ONLINE+ D:\ORACLE\PRD\SAPDATA2\SR3_9\SR3.DATA9 2097160192 12 3 NOLINK FILE 10485760000 20971520 8192
PSAPSR3 ONLINE* ONLINE+ D:\ORACLE\PRD\SAPDATA3\SR3_11\SR3.DATA11 2202017792 14 3 NOLINK FILE 10485760000 20971520 8192
PSAPSR3 ONLINE* ONLINE+ D:\ORACLE\PRD\SAPDATA3\SR3_12\SR3.DATA12 2139103232 15 3 NOLINK FILE 10485760000 20971520 8192
PSAPSR3 ONLINE* ONLINE+ D:\ORACLE\PRD\SAPDATA3\SR3_13\SR3.DATA13 2139103232 16 3 NOLINK FILE 10485760000 20971520 8192
PSAPSR3 ONLINE* ONLINE+ D:\ORACLE\PRD\SAPDATA3\SR3_14\SR3.DATA14 2222989312 17 3 NOLINK FILE 10485760000 20971520 8192
PSAPSR3 ONLINE* ONLINE+ D:\ORACLE\PRD\SAPDATA3\SR3_15\SR3.DATA15 2097160192 18 3 NOLINK FILE 10485760000 20971520 8192
PSAPSR3 ONLINE* ONLINE+ D:\ORACLE\PRD\SAPDATA4\SR3_16\SR3.DATA16 2097160192 19 3 NOLINK FILE 10485760000 20971520 8192
PSAPSR3 ONLINE* ONLINE+ D:\ORACLE\PRD\SAPDATA4\SR3_17\SR3.DATA17 2097160192 20 3 NOLINK FILE 10485760000 20971520 8192
PSAPSR3 ONLINE* ONLINE+ D:\ORACLE\PRD\SAPDATA4\SR3_18\SR3.DATA18 2097160192 21 3 NOLINK FILE 10485760000 20971520 8192
PSAPSR3 ONLINE* ONLINE+ D:\ORACLE\PRD\SAPDATA4\SR3_19\SR3.DATA19 2097160192 22 3 NOLINK FILE 10485760000 20971520 8192
PSAPSR3 ONLINE* ONLINE+ D:\ORACLE\PRD\SAPDATA4\SR3_20\SR3.DATA20 2097160192 23 3 NOLINK FILE 10485760000 20971520 8192
PSAPSR3 ONLINE* ONLINE+ D:\ORACLE\PRD\SAPDATA4\SR3_21\SR3.DATA21 4294975488 47 3 NOLINK FILE 10485760000 20971520 8192
PSAPSR3700 ONLINE* ONLINE+ D:\ORACLE\PRD\SAPDATA1\SR3700_1\SR3700.DATA1 3439337472 24 3 NOLINK FILE 10485760000 20971520 8192
PSAPSR3700 ONLINE* ONLINE+ D:\ORACLE\PRD\SAPDATA1\SR3700_2\SR3700.DATA2 3502252032 25 3 NOLINK FILE 10485760000 20971520 8192
PSAPSR3700 ONLINE* ONLINE+ D:\ORACLE\PRD\SAPDATA1\SR3700_3\SR3700.DATA3 3628081152 26 3 NOLINK FILE 10485760000 20971520 8192
PSAPSR3700 ONLINE* ONLINE+ D:\ORACLE\PRD\SAPDATA1\SR3700_4\SR3700.DATA4 3565166592 27 3 NOLINK FILE 10485760000 20971520 8192
PSAPSR3700 ONLINE* ONLINE+ D:\ORACLE\PRD\SAPDATA2\SR3700_5\SR3700.DATA5 3460308992 28 3 NOLINK FILE 10485760000 20971520 8192
PSAPSR3700 ONLINE* ONLINE+ D:\ORACLE\PRD\SAPDATA2\SR3700_6\SR3700.DATA6 3187679232 29 3 NOLINK FILE 10485760000 20971520 8192
PSAPSR3700 ONLINE* ONLINE+ D:\ORACLE\PRD\SAPDATA2\SR3700_7\SR3700.DATA7 3103793152 30 3 NOLINK FILE 10485760000 20971520 8192
PSAPSR3700 ONLINE* ONLINE+ D:\ORACLE\PRD\SAPDATA2\SR3700_8\SR3700.DATA8 3103793152 31 3 NOLINK FILE 10485760000 20971520 8192
PSAPSR3700 ONLINE* ONLINE+ D:\ORACLE\PRD\SAPDATA3\SR3700_10\SR3700.DATA10 2956992512 33 3 NOLINK FILE 10485760000 20971520 8192
PSAPSR3700 ONLINE* ONLINE+ D:\ORACLE\PRD\SAPDATA3\SR3700_11\SR3700.DATA11 2873106432 34 3 NOLINK FILE 10485760000 20971520 8192
PSAPSR3700 ONLINE* ONLINE+ D:\ORACLE\PRD\SAPDATA3\SR3700_12\SR3700.DATA12 2810191872 35 3 NOLINK FILE 10485760000 20971520 8192
PSAPSR3700 ONLINE* ONLINE+ D:\ORACLE\PRD\SAPDATA3\SR3700_9\SR3700.DATA9 3061850112 32 3 NOLINK FILE 10485760000 20971520 8192
PSAPSR3700 ONLINE* ONLINE+ D:\ORACLE\PRD\SAPDATA4\SR3700_13\SR3700.DATA13 2977964032 36 3 NOLINK FILE 10485760000 20971520 8192
PSAPSR3700 ONLINE* ONLINE+ D:\ORACLE\PRD\SAPDATA4\SR3700_14\SR3700.DATA14 3124764672 37 3 NOLINK FILE 10485760000 20971520 8192
PSAPSR3700 ONLINE* ONLINE+ D:\ORACLE\PRD\SAPDATA4\SR3700_15\SR3700.DATA15 3124764672 38 3 NOLINK FILE 10485760000 20971520 8192
PSAPSR3700 ONLINE* ONLINE+ D:\ORACLE\PRD\SAPDATA4\SR3700_16\SR3700.DATA16 3124764672 39 3 NOLINK FILE 10485760000 20971520 8192
PSAPSR3700 ONLINE* ONLINE+ D:\ORACLE\PRD\SAPDATA4\SR3700_17\SR3700.DATA17 8925487104 44 3 NOLINK FILE 10485760000 20971520 8192
PSAPSR3700 ONLINE* ONLINE+ D:\ORACLE\PRD\SAPDATA4\SR3700_18\SR3700.DATA18 8589942784 46 3 NOLINK FILE 10485760000 20971520 8192
PSAPSR3700 ONLINE* ONLINE+ D:\ORACLE\PRD\SAPDATA4\SR3700_19\SR3700.DATA19 4294975488 48 3 NOLINK FILE 10485760000 20971520 8192
PSAPSR3700 ONLINE* ONLINE+ D:\ORACLE\PRD\SAPDATA4\SR3700_20\SR3700.DATA20 2147491840 49 3 NOLINK FILE 10485760000 20971520 8192
PSAPSR3DB ONLINE* ONLINE+ D:\ORACLE\PRD\SAPDATA4\SR3DB_1\SR3DB.DATA1 2097160192 41 3 NOLINK FILE 10485760000 20971520 8192
PSAPSR3DB ONLINE* ONLINE+ D:\ORACLE\PRD\SAPDATA4\SR3DB_2\SR3DB.DATA2 2097160192 42 3 NOLINK FILE 10485760000 20971520 8192
PSAPSR3DB ONLINE* ONLINE+ D:\ORACLE\PRD\SAPDATA4\SR3DB_3\SR3DB.DATA3 1048584192 43 3 NOLINK FILE 10485760000 20971520 8192
PSAPSR3USR ONLINE* ONLINE+ D:\ORACLE\PRD\SAPDATA1\SR3USR_1\SR3USR.DATA1 20979712 40 3 NOLINK FILE 10485760000 20971520 8192
PSAPTEMP ONLINE# ONLINE+ D:\ORACLE\PRD\SAPDATA2\TEMP_1\TEMP.DATA1 3586138112 -1 3 NOLINK FILE 10485760000 20971520 8192
PSAPUNDO ONLINE- ONLINE+ D:\ORACLE\PRD\SAPDATA3\UNDO_1\UNDO.DATA1 9080676352 2 3 NOLINK FILE 10485760000 20971520 8192
PSAPUNDO ONLINE- ONLINE D:\ORACLE\PRD\SAPDATA3\UNDO_2\UNDO.DATA2 1073750016 45 3 NOLINK FILE 0 0 8192
SYSAUX ONLINE* ONLINE+ D:\ORACLE\PRD\SAPDATA1\SYSAUX_1\SYSAUX.DATA1 419438592 3 3 NOLINK FILE 10485760000 20971520 8192
SYSTEM ONLINE* SYSTEM+ D:\ORACLE\PRD\SAPDATA1\SYSTEM_1\SYSTEM.DATA1 880812032 1 3 NOLINK FILE 10485760000 20971520 8192
BR0119I Redo log files
File Size Group Device Status Link Type
H:\ORACLE\PRD\ORIGLOGA\LOG_G11M1.DBF 52429312 1 7 INUSE NOLINK FILE
F:\ORACLE\PRD\MIRRLOGA\LOG_G11M2.DBF 52429312 1 5 INUSE NOLINK FILE
H:\ORACLE\PRD\ORIGLOGB\LOG_G12M1.DBF 52429312 2 7 INUSE NOLINK FILE
F:\ORACLE\PRD\MIRRLOGB\LOG_G12M2.DBF 52429312 2 5 INUSE NOLINK FILE
H:\ORACLE\PRD\ORIGLOGA\LOG_G13M1.DBF 52429312 3 7 INUSE NOLINK FILE
F:\ORACLE\PRD\MIRRLOGA\LOG_G13M2.DBF 52429312 3 5 INUSE NOLINK FILE
H:\ORACLE\PRD\ORIGLOGB\LOG_G14M1.DBF 52429312 4 7 INUSE NOLINK FILE
F:\ORACLE\PRD\MIRRLOGB\LOG_G14M2.DBF 52429312 4 5 INUSE NOLINK FILE
BR0120I Control files
File Size Id. Device Link Type
H:\oracle\PRD\origlogA\cntrl\cntlrPRD.dbf 21905408 0 7 NOLINK FILE
H:\oracle\PRD\origlogB\cntrl\cntrlPRD.dbf 21905408 0 7 NOLINK FILE
D:\oracle\PRD\sapdata1\cntrl\cntrlPRD.dbf 21905408 0 3 NOLINK FILE
BR0616I Tablespaces in table TSORA for SAP owner SAPSR3:
PSAPSR3, PSAPSR3700, PSAPSR3USR
BR0280I BRBACKUP time stamp: 2008-07-17 00.00.48
BR0057I Backup of database: PRD
BR0058I BRBACKUP action ID: bdyjmnib
BR0059I BRBACKUP function ID: and
BR0110I Backup mode: ALL
BR0077I Database file for backup: D:\oracle\PRD\sapbackup\CNTRLPRD.DBF
BR0061I 50 files found for backup, total size 131949.273 MB
BR0143I Backup type: online_cons
BR0111I Files will be compressed
BR0130I Backup device type: disk
BR0106I Files will be saved on disk in directory: F:\PRDBACKUP\bdyjmnib
BR0136I Verify option set - double work to do
BR0280I BRBACKUP time stamp: 2008-07-17 00.00.48
BR0256I Enter 'c[ont]' to continue, 's[top]' to cancel BRBACKUP:
BR0280I BRBACKUP time stamp: 2008-07-17 00.00.48
BR0255W Cannot read from standard input
BR0370I Directory F:\PRDBACKUP\bdyjmnib created
BR0370I Directory F:\PRDBACKUP\PRD created
BR0202I Saving init_ora
BR0203I to F:\PRDBACKUP\PRD ...
BR0202I Saving D:\oracle\PRD\102\database\initPRD.sap
BR0203I to F:\PRDBACKUP\PRD ...
BR0280I BRBACKUP time stamp: 2008-07-17 00.00.48
BR0198I Profiles saved successfully
BR0280I BRBACKUP time stamp: 2008-07-17 00.00.48
BR0315I 'Alter tablespace PSAPSR3 begin backup' successful
BR0201I Compressing D:\ORACLE\PRD\SAPDATA1\SR3_1\SR3.DATA1
BR0203I to F:\PRDBACKUP\bdyjmnib\SR3.DATA1.Z ...
#FILE..... D:\ORACLE\PRD\SAPDATA1\SR3_1\SR3.DATA1
#SAVED.... F:\PRDBACKUP\bdyjmnib\SR3.DATA1.Z #1/1 10.4425:1 200829206
BR0280I BRBACKUP time stamp: 2008-07-17 00.03.12
BR0063I 1 of 100 files processed - 2000.008 MB of 263898.547 MB done
BR0204I Percentage done: 0.76%, estimated end time: 5:17
BR0001I __________________________________________________
BR0201I Compressing D:\ORACLE\PRD\SAPDATA1\SR3_2\SR3.DATA2
BR0203I to F:\PRDBACKUP\bdyjmnib\SR3.DATA2.Z ...
#FILE..... D:\ORACLE\PRD\SAPDATA1\SR3_2\SR3.DATA2
#SAVED.... F:\PRDBACKUP\bdyjmnib\SR3.DATA2.Z #1/2 10.2132:1 205338055
BR0280I BRBACKUP time stamp: 2008-07-17 00.05.37
BR0063I 2 of 100 files processed - 4000.016 MB of 263898.547 MB done
BR0204I Percentage done: 1.52%, estimated end time: 5:18
BR0001I *_________________________________________________
BR0201I Compressing D:\ORACLE\PRD\SAPDATA1\SR3_3\SR3.DATA3
BR0203I to F:\PRDBACKUP\bdyjmnib\SR3.DATA3.Z ...
#FILE..... D:\ORACLE\PRD\SAPDATA1\SR3_3\SR3.DATA3
#SAVED.... F:\PRDBACKUP\bdyjmnib\SR3.DATA3.Z #1/3 9.6322:1 217723578
BR0280I BRBACKUP time stamp: 2008-07-17 00.08.04
BR0063I 3 of 100 files processed - 6000.023 MB of 263898.547 MB done
BR0204I Percentage done: 2.27%, estimated end time: 5:20
BR0001I *_________________________________________________
BR0201I Compressing D:\ORACLE\PRD\SAPDATA1\SR3_4\SR3.DATA4
BR0203I to F:\PRDBACKUP\bdyjmnib\SR3.DATA4.Z ...
#FILE..... D:\ORACLE\PRD\SAPDATA1\SR3_4\SR3.DATA4
#SAVED.... F:\PRDBACKUP\bdyjmnib\SR3.DATA4.Z #1/4 9.4017:1 223062356
BR0280I BRBACKUP time stamp: 2008-07-17 00.10.34
BR0063I 4 of 100 files processed - 8000.031 MB of 263898.547 MB done
BR0204I Percentage done: 3.03%, estimated end time: 5:22
BR0001I **________________________________________________
BR0201I Compressing D:\ORACLE\PRD\SAPDATA1\SR3_5\SR3.DATA5
BR0203I to F:\PRDBACKUP\bdyjmnib\SR3.DATA5.Z ...
#FILE..... D:\ORACLE\PRD\SAPDATA1\SR3_5\SR3.DATA5
#SAVED.... F:\PRDBACKUP\bdyjmnib\SR3.DATA5.Z #1/5 7.1553:1 293090497
BR0280I BRBACKUP time stamp: 2008-07-17 00.13.17
BR0063I 5 of 100 files processed - 10000.039 MB of 263898.547 MB done
BR0204I Percentage done: 3.79%, estimated end time: 5:30
BR0001I **________________________________________________
BR0201I Compressing D:\ORACLE\PRD\SAPDATA2\SR3_10\SR3.DATA10
BR0203I to F:\PRDBACKUP\bdyjmnib\SR3.DATA10.Z ...
#FILE..... D:\ORACLE\PRD\SAPDATA2\SR3_10\SR3.DATA10
#SAVED.... F:\PRDBACKUP\bdyjmnib\SR3.DATA10.Z #1/6 7.8803:1 274111845
BR0280I BRBACKUP time stamp: 2008-07-17 00.16.04
BR0063I 6 of 100 files processed - 12060.047 MB of 263898.547 MB done
BR0204I Percentage done: 4.57%, estimated end time: 5:34
BR0001I **________________________________________________
BR0201I Compressing D:\ORACLE\PRD\SAPDATA2\SR3_6\SR3.DATA6
BR0203I to F:\PRDBACKUP\bdyjmnib\SR3.DATA6.Z ...
#FILE..... D:\ORACLE\PRD\SAPDATA2\SR3_6\SR3.DATA6
#SAVED.... F:\PRDBACKUP\bdyjmnib\SR3.DATA6.Z #1/7 7.2325:1 289963615
BR0280I BRBACKUP time stamp: 2008-07-17 00.18.44
BR0063I 7 of 100 files processed - 14060.055 MB of 263898.547 MB done
BR0204I Percentage done: 5.33%, estimated end time: 5:37
BR0001I ***_______________________________________________
BR0201I Compressing D:\ORACLE\PRD\SAPDATA2\SR3_7\SR3.DATA7
BR0203I to F:\PRDBACKUP\bdyjmnib\SR3.DATA7.Z ...
#FILE..... D:\ORACLE\PRD\SAPDATA2\SR3_7\SR3.DATA7
#SAVED.... F:\PRDBACKUP\bdyjmnib\SR3.DATA7.Z #1/8 7.5405:1 278117799
BR0280I BRBACKUP time stamp: 2008-07-17 00.21.25
BR0063I 8 of 100 files processed - 16060.063 MB of 263898.547 MB done
BR0204I Percentage done: 6.09%, estimated end time: 5:39
BR0001I ***_______________________________________________
BR0201I Compressing D:\ORACLE\PRD\SAPDATA2\SR3_8\SR3.DATA8
BR0203I to F:\PRDBACKUP\bdyjmnib\SR3.DATA8.Z ...
#FILE..... D:\ORACLE\PRD\SAPDATA2\SR3_8\SR3.DATA8
#SAVED.... F:\PRDBACKUP\bdyjmnib\SR3.DATA8.Z #1/9 7.6552:1 273953946
BR0280I BRBACKUP time stamp: 2008-07-17 00.24.08
BR0063I 9 of 100 files processed - 18060.070 MB of 263898.547 MB done
BR0204I Percentage done: 6.84%, estimated end time: 5:41
BR0001I ***_______________________________________________
BR0201I Compressing D:\ORACLE\PRD\SAPDATA2\SR3_9\SR3.DATA9
BR0203I to F:\PRDBACKUP\bdyjmnib\SR3.DATA9.Z ...
#FILE..... D:\ORACLE\PRD\SAPDATA2\SR3_9\SR3.DATA9
#SAVED.... F:\PRDBACKUP\bdyjmnib\SR3.DATA9.Z #1/10 7.8306:1 267815733
BR0280I BRBACKUP time stamp: 2008-07-17 00.26.51
BR0063I 10 of 100 files processed - 20060.078 MB of 263898.547 MB done
BR0204I Percentage done: 7.60%, estimated end time: 5:43
BR0001I ****______________________________________________
BR0201I Compressing D:\ORACLE\PRD\SAPDATA3\SR3_11\SR3.DATA11
BR0203I to F:\PRDBACKUP\bdyjmnib\SR3.DATA11.Z ...
#FILE..... D:\ORACLE\PRD\SAPDATA3\SR3_11\SR3.DATA11
#SAVED.... F:\PRDBACKUP\bdyjmnib\SR3.DATA11.Z #1/11 7.6512:1 287801651
BR0280I BRBACKUP time stamp: 2008-07-17 00.29.43
BR0063I 11 of 100 files processed - 22160.086 MB of 263898.547 MB done
BR0204I Percentage done: 8.40%, estimated end time: 5:45
BR0001I ****______________________________________________
BR0201I Compressing D:\ORACLE\PRD\SAPDATA3\SR3_12\SR3.DATA12
BR0203I to F:\PRDBACKUP\bdyjmnib\SR3.DATA12.Z ...
#FILE..... D:\ORACLE\PRD\SAPDATA3\SR3_12\SR3.DATA12
#SAVED.... F:\PRDBACKUP\bdyjmnib\SR3.DATA12.Z #1/12 7.4549:1 286939513
BR0280I BRBACKUP time stamp: 2008-07-17 00.32.32
BR0063I 12 of 100 files processed - 24200.094 MB of 263898.547 MB done
BR0204I Percentage done: 9.17%, estimated end time: 5:46
BR0001I *****_____________________________________________
BR0201I Compressing D:\ORACLE\PRD\SAPDATA3\SR3_13\SR3.DATA13
BR0203I to F:\PRDBACKUP\bdyjmnib\SR3.DATA13.Z ...
#FILE..... D:\ORACLE\PRD\SAPDATA3\SR3_13\SR3.DATA13
#SAVED.... F:\PRDBACKUP\bdyjmnib\SR3.DATA13.Z #1/13 7.3869:1 289579982
BR0280I BRBACKUP time stamp: 2008-07-17 00.35.22
BR0063I 13 of 100 files processed - 26240.102 MB of 263898.547 MB done
BR0204I Percentage done: 9.94%, estimated end time: 5:48
BR0001I *****_____________________________________________
BR0201I Compressing D:\ORACLE\PRD\SAPDATA3\SR3_14\SR3.DATA14
BR0203I to F:\PRDBACKUP\bdyjmnib\SR3.DATA14.Z ...
#FILE..... D:\ORACLE\PRD\SAPDATA3\SR3_14\SR3.DATA14
#SAVED.... F:\PRDBACKUP\bdyjmnib\SR3.DATA14.Z #1/14 10.4368:1 212996281
BR0280I BRBACKUP time stamp: 2008-07-17 00.37.58
BR0063I 14 of 100 files processed - 28360.109 MB of 263898.547 MB done
BR0204I Percentage done: 10.75%, estimated end time: 5:46
BR0001I *****_____________________________________________
BR0201I Compressing D:\ORACLE\PRD\SAPDATA3\SR3_15\SR3.DATA15
BR0203I to F:\PRDBACKUP\bdyjmnib\SR3.DATA15.Z ...
#FILE..... D:\ORACLE\PRD\SAPDATA3\SR3_15\SR3.DATA15
#SAVED.... F:\PRDBACKUP\bdyjmnib\SR3.DATA15.Z #1/15 9.5302:1 220055261
BR0280I BRBACKUP time stamp: 2008-07-17 00.40.29
BR0063I 15 of 100 files processed - 30360.117 MB of 263898.547 MB done
BR0204I Percentage done: 11.50%, estimated end time: 5:45
BR0001I ******____________________________________________
BR0201I Compressing D:\ORACLE\PRD\SAPDATA4\SR3_16\SR3.DATA16
BR0203I to F:\PRDBACKUP\bdyjmnib\SR3.DATA16.Z ...
#FILE..... D:\ORACLE\PRD\SAPDATA4\SR3_16\SR3.DATA16
#SAVED.... F:\PRDBACKUP\bdyjmnib\SR3.DATA16.Z #1/16 7.1527:1 293197730
BR0280I BRBACKUP time stamp: 2008-07-17 00.43.16
BR0063I 16 of 100 files processed - 32360.125 MB of 263898.547 MB done
BR0204I Percentage done: 12.26%, estimated end time: 5:47
BR0001I ******____________________________________________
BR0201I Compressing D:\ORACLE\PRD\SAPDATA4\SR3_17\SR3.DATA17
BR0203I to F:\PRDBACKUP\bdyjmnib\SR3.DATA17.Z ...
#FILE..... D:\ORACLE\PRD\SAPDATA4\SR3_17\SR3.DATA17
#SAVED.... F:\PRDBACKUP\bdyjmnib\SR3.DATA17.Z #1/17 7.3970:1 283515075
BR0280I BRBACKUP time stamp: 2008-07-17 00.46.03
BR0063I 17 of 100 files processed - 34360.133 MB of 263898.547 MB done
BR0204I Percentage done: 13.02%, estimated end time: 5:48
BR0001I *******___________________________________________
BR0201I Compressing D:\ORACLE\PRD\SAPDATA4\SR3_18\SR3.DATA18
BR0203I to F:\PRDBACKUP\bdyjmnib\SR3.DATA18.Z ...
#FILE..... D:\ORACLE\PRD\SAPDATA4\SR3_18\SR3.DATA18
#SAVED.... F:\PRDBACKUP\bdyjmnib\SR3.DATA18.Z #1/18 11.5406:1 181719891
BR0280I BRBACKUP time stamp: 2008-07-17 00.48.21
BR0063I 18 of 100 files processed - 36360.141 MB of 263898.547 MB done
BR0204I Percentage done: 13.78%, estimated end time: 5:45
BR0001I *******___________________________________________
BR0201I Compressing D:\ORACLE\PRD\SAPDATA4\SR3_19\SR3.DATA19
BR0203I to F:\PRDBACKUP\bdyjmnib\SR3.DATA19.Z ...
#FILE..... D:\ORACLE\PRD\SAPDATA4\SR3_19\SR3.DATA19
#SAVED.... F:\PRDBACKUP\bdyjmnib\SR3.DATA19.Z #1/19 11.1634:1 187859619
BR0280I BRBACKUP time stamp: 2008-07-17 00.50.36
BR0063I 19 of 100 files processed - 38360.148 MB of 263898.547 MB done
BR0204I Percentage done: 14.54%, estimated end time: 5:43
BR0001I *******___________________________________________
BR0201I Compressing D:\ORACLE\PRD\SAPDATA4\SR3_20\SR3.DATA20
BR0203I to F:\PRDBACKUP\bdyjmnib\SR3.DATA20.Z ...
#FILE..... D:\ORACLE\PRD\SAPDATA4\SR3_20\SR3.DATA20
#SAVED.... F:\PRDBACKUP\bdyjmnib\SR3.DATA20.Z #1/20 10.4747:1 200212728
BR0280I BRBACKUP time stamp: 2008-07-17 00.52.54
BR0063I 20 of 100 files processed - 40360.156 MB of 263898.547 MB done
BR0204I Percentage done: 15.29%, estimated end time: 5:41
BR0001I ********__________________________________________
BR0201I Compressing D:\ORACLE\PRD\SAPDATA4\SR3_21\SR3.DATA21
BR0203I to F:\PRDBACKUP\bdyjmnib\SR3.DATA21.Z ...
#FILE..... D:\ORACLE\PRD\SAPDATA4\SR3_21\SR3.DATA21
#SAVED.... F:\PRDBACKUP\bdyjmnib\SR3.DATA21.Z #1/21 48.4581:1 88632774
BR0280I BRBACKUP time stamp: 2008-07-17 00.57.13
BR0063I 21 of 100 files processed - 44456.164 MB of 263898.547 MB done
BR0204I Percentage done: 16.85%, estimated end time: 5:35
BR0001I ********__________________________________________
BR0280I BRBACKUP time stamp: 2008-07-17 00.57.13
BR0317I 'Alter tablespace PSAPSR3 end backup' successful
BR0280I BRBACKUP time stamp: 2008-07-17 00.57.14
BR0315I 'Alter tablespace PSAPSR3700 begin backup' successful
BR0201I Compressing D:\ORACLE\PRD\SAPDATA1\SR3700_1\SR3700.DATA1
BR0203I to F:\PRDBACKUP\bdyjmnib\SR3700.DATA1.Z ...
#FILE..... D:\ORACLE\PRD\SAPDATA1\SR3700_1\SR3700.DATA1
#SAVED.... F:\PRDBACKUP\bdyjmnib\SR3700.DATA1.Z #1/22 5.4819:1 627401795
BR0280I BRBACKUP time stamp: 2008-07-17 01.02.05
BR0063I 22 of 100 files processed - 47736.172 MB of 263898.547 MB done
BR0204I Percentage done: 18.09%, estimated end time: 5:39
BR0001I *********_________________________________________
BR0201I Compressing D:\ORACLE\PRD\SAPDATA1\SR3700_2\SR3700.DATA2
BR0203I to F:\PRDBACKUP\bdyjmnib\SR3700.DATA2.Z ...
#FILE..... D:\ORACLE\PRD\SAPDATA1\SR3700_2\SR3700.DATA2
#SAVED.... F:\PRDBACKUP\bdyjmnib\SR3700.DATA2.Z #1/23 4.8358:1 724237070
BR0280I BRBACKUP time stamp: 2008-07-17 01.07.58
BR0063I 23 of 100 files processed - 51076.180 MB of 263898.547 MB done
BR0204I Percentage done: 19.35%, estimated end time: 5:47
BR0001I **********________________________________________
BR0201I Compressing D:\ORACLE\PRD\SAPDATA1\SR3700_3\SR3700.DATA3
BR0203I to F:\PRDBACKUP\bdyjmnib\SR3700.DATA3.Z ...
#FILE..... D:\ORACLE\PRD\SAPDATA1\SR3700_3\SR3700.DATA3
#SAVED.... F:\PRDBACKUP\bdyjmnib\SR3700.DATA3.Z #1/24 4.5756:1 792914455
BR0280I BRBACKUP time stamp: 2008-07-17 01.13.35
BR0063I 24 of 100 files processed - 54536.188 MB of 263898.547 MB done
BR0204I Percentage done: 20.67%, estimated end time: 5:52
BR0001I **********________________________________________
BR0201I Compressing D:\ORACLE\PRD\SAPDATA1\SR3700_4\SR3700.DATA4
BR0203I to F:\PRDBACKUP\bdyjmnib\SR3700.DATA4.Z ...
#FILE..... D:\ORACLE\PRD\SAPDATA1\SR3700_4\SR3700.DATA4
#SAVED.... F:\PRDBACKUP\bdyjmnib\SR3700.DATA4.Z #1/25 4.5860:1 777397525
BR0280I BRBACKUP time stamp: 2008-07-17 01.19.13
BR0063I 25 of 100 files processed - 57936.195 MB of 263898.547 MB done
BR0204I Percentage done: 21.95%, estimated end time: 5:57
BR0001I ***********_______________________________________
BR0201I Compressing D:\ORACLE\PRD\SAPDATA2\SR3700_5\SR3700.DATA5
BR0203I to F:\PRDBACKUP\bdyjmnib\SR3700.DATA5.Z ...
#FILE..... D:\ORACLE\PRD\SAPDATA2\SR3700_5\SR3700.DATA5
#SAVED.... F:\PRDBACKUP\bdyjmnib\SR3700.DATA5.Z #1/26 4.4184:1 783153938
BR0280I BRBACKUP time stamp: 2008-07-17 01.24.54
BR0063I 26 of 100 files processed - 61236.203 MB of 263898.547 MB done
BR0204I Percentage done: 23.20%, estimated end time: 6:03
BR0001I ************______________________________________
BR0201I Compressing D:\ORACLE\PRD\SAPDATA2\SR3700_6\SR3700.DATA6
BR0203I to F:\PRDBACKUP\bdyjmnib\SR3700.DATA6.Z ...
#FILE..... D:\ORACLE\PRD\SAPDATA2\SR3700_6\SR3700.DATA6
#SAVED.... F:\PRDBACKUP\bdyjmnib\SR3700.DATA6.Z #1/27 4.7599:1 669696481
BR0280I BRBACKUP time stamp: 2008-07-17 01.29.56
BR0063I 27 of 100 files processed - 64276.211 MB of 263898.547 MB done
BR0204I Percentage done: 24.36%, estimated end time: 6:06
BR0001I ************______________________________________
BR0201I Compressing D:\ORACLE\PRD\SAPDATA2\SR3700_7\SR3700.DATA7
BR0203I to F:\PRDBACKUP\bdyjmnib\SR3700.DATA7.Z ...
#FILE..... D:\ORACLE\PRD\SAPDATA2\SR3700_7\SR3700.DATA7
#SAVED.... F:\PRDBACKUP\bdyjmnib\SR3700.DATA7.Z #1/28 4.4786:1 693030496
BR0280I BRBACKUP time stamp: 2008-07-17 01.34.41
BR0063I 28 of 100 files processed - 67236.219 MB of 263898.547 MB done
BR0204I Percentage done: 25.48%, estimated end time: 6:09
BR0001I *************_____________________________________
BR0201I Compressing D:\ORACLE\PRD\SAPDATA2\SR3700_8\SR3700.DATA8
BR0203I to F:\PRDBACKUP\bdyjmnib\SR3700.DATA8.Z ...
#FILE..... D:\ORACLE\PRD\SAPDATA2\SR3700_8\SR3700.DATA8
#SAVED.... F:\PRDBACKUP\bdyjmnib\SR3700.DATA8.Z #1/29 5.0475:1 614922935
BR0280I BRBACKUP time stamp: 2008-07-17 01.39.18
BR0063I 29 of 100 files processed - 70196.227 MB of 263898.547 MB done
BR0204I Percentage done: 26.60%, estimated end time: 6:11
BR0001I *************_____________________________________
BR0201I Compressing D:\ORACLE\PRD\SAPDATA3\SR3700_10\SR3700.DATA10
BR0203I to F:\PRDBACKUP\bdyjmnib\SR3700.DATA10.Z ...
#FILE..... D:\ORACLE\PRD\SAPDATA3\SR3700_10\SR3700.DATA10
#SAVED.... F:\PRDBACKUP\bdyjmnib\SR3700.DATA10.Z #1/30 5.1235:1 577147267
BR0280I BRBACKUP time stamp: 2008-07-17 01.43.51
BR0063I 30 of 100 files processed - 73016.234 MB of 263898.547 MB done
BR0204I Percentage done: 27.67%, estimated end time: 6:13
BR0001I **************____________________________________
BR0201I Compressing D:\ORACLE\PRD\SAPDATA3\SR3700_11\SR3700.DATA11
BR0203I to F:\PRDBACKUP\bdyjmnib\SR3700.DATA11.Z ...
#FILE..... D:\ORACLE\PRD\SAPDATA3\SR3700_11\SR3700.DATA11
#SAVED.... F:\PRDBACKUP\bdyjmnib\SR3700.DATA11.Z #1/31 5.3053:1 541550053
BR0280I BRBACKUP time stamp: 2008-07-17 01.48.22
BR0063I 31 of 100 files processed - 75756.242 MB of 263898.547 MB done
BR0204I Percentage done: 28.71%, estimated end time: 6:15
BR0001I **************____________________________________
BR0201I Compressing D:\ORACLE\PRD\SAPDATA3\SR3700_12\SR3700.DATA12
BR0203I to F:\PRDBACKUP\bdyjmnib\SR3700.DATA12.Z ...
#FILE..... D:\ORACLE\PRD\SAPDATA3\SR3700_12\SR3700.DATA12
#SAVED.... F:\PRDBACKUP\bdyjmnib\SR3700.DATA12.Z #1/32 5.3637:1 523928567
BR0280I BRBACKUP time stamp: 2008-07-17 01.52.31
BR0063I 32 of 100 files processed - 78436.250 MB of 263898.547 MB done
BR0204I Percentage done: 29.72%, estimated end time: 6:16
BR0001I ***************___________________________________
BR0201I Compressing D:\ORACLE\PRD\SAPDATA3\SR3700_9\SR3700.DATA9
BR0203I to F:\PRDBACKUP\bdyjmnib\SR3700.DATA9.Z ...
#FILE..... D:\ORACLE\PRD\SAPDATA3\SR3700_9\SR3700.DATA9
#SAVED.... F:\PRDBACKUP\bdyjmnib\SR3700.DATA9.Z #1/33 5.1897:1 589985899
BR0280I BRBACKUP time stamp: 2008-07-17 01.57.48
BR0063I 33 of 100 files processed - 81356.258 MB of 263898.547 MB done
BR0204I Percentage done: 30.83%, estimated end time: 6:20
BR0001I ***************___________________________________
BR0201I Compressing D:\ORACLE\PRD\SAPDATA4\SR3700_13\SR3700.DATA13
BR0203I to F:\PRDBACKUP\bdyjmnib\SR3700.DATA13.Z ...
#FILE..... D:\ORACLE\PRD\SAPDATA4\SR3700_13\SR3700.DATA13
#SAVED.... F:\PRDBACKUP\bdyjmnib\SR3700.DATA13.Z #1/34 5.3113:1 560686123
BR0280I BRBACKUP time stamp: 2008-07-17 02.02.11
BR0063I 34 of 100 files processed - 84196.266 MB of 263898.547 MB done
BR0204I Percentage done: 31.90%, estimated end time: 6:21
BR0001I ****************__________________________________
BR0201I Compressing D:\ORACLE\PRD\SAPDATA4\SR3700_14\SR3700.DATA14
BR0203I to F:\PRDBACKUP\bdyjmnib\SR3700.DATA14.Z ...
#FILE..... D:\ORACLE\PRD\SAPDATA4\SR3700_14\SR3700.DATA14
#SAVED.... F:\PRDBACKUP\bdyjmnib\SR3700.DATA14.Z #1/35 4.8881:1 639264649
BR0280I BRBACKUP time stamp: 2008-07-17 02.07.51
BR0063I 35 of 100 files processed - 87176.273 MB of 263898.547 MB done
BR0204I Percentage done: 33.03%, estimated end time: 6:25
BR0001I *****************_________________________________
BR0201I Compressing D:\ORACLE\PRD\SAPDATA4\SR3700_15\SR3700.DATA15
BR0203I to F:\PRDBACKUP\bdyjmnib\SR3700.DATA15.Z ...
#FILE..... D:\ORACLE\PRD\SAPDATA4\SR3700_15\SR3700.DATA15
#SAVED.... F:\PRDBACKUP\bdyjmnib\SR3700.DATA15.Z #1/36 5.2020:1 600683811
BR0280I BRBACKUP time stamp: 2008-07-17 02.12.16
BR0063I 36 of 100 files processed - 90156.281 MB of 263898.547 MB done
BR0204I Percentage done: 34.16%, estimated end time: 6:25
BR0001I *****************_________________________________
BR0201I Compressing D:\ORACLE\PRD\SAPDATA4\SR3700_16\SR3700.DATA16
BR0203I to F:\PRDBACKUP\bdyjmnib\SR3700.DATA16.Z ...
#FILE..... D:\ORACLE\PRD\SAPDATA4\SR3700_16\SR3700.DATA16
#SAVED.... F:\PRDBACKUP\bdyjmnib\SR3700.DATA16.Z #1/37 5.1273:1 609440417
BR0280I BRBACKUP time stamp: 2008-07-17 02.16.47
BR0063I 37 of 100 files processed - 93136.289 MB of 263898.547 MB done
BR0204I Percentage done: 35.29%, estimated end time: 6:26
BR0001I ******************________________________________
BR0201I Compressing D:\ORACLE\PRD\SAPDATA4\SR3700_17\SR3700.DATA17
BR0203I to F:\PRDBACKUP\bdyjmnib\SR3700.DATA17.Z ...
#FILE..... D:\ORACLE\PRD\SAPDATA4\SR3700_17\SR3700.DATA17
#SAVED.... F:\PRDBACKUP\bdyjmnib\SR3700.DATA17.Z #1/38 3.8067:1 2344670180
BR0280I BRBACKUP time stamp: 2008-07-17 02.34.30
BR0063I 38 of 100 files processed - 101648.297 MB of 263898.547 MB done
BR0204I Percentage done: 38.52%, estimated end time: 6:39
BR0001I *******************_______________________________
BR0201I Compressing D:\ORACLE\PRD\SAPDATA4\SR3700_18\SR3700.DATA18
BR0203I to F:\PRDBACKUP\bdyjmnib\SR3700.DATA18.Z ...
BR0280I BRBACKUP time stamp: 2008-07-17 02.58.41
BR0266E Program 'D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\mkszip -c D:\ORACLE\PRD\SAPDATA4\SR3700_18\SR3700.DATA18 > F:\PRDBACKUP\bdyjmnib\SR3700.DATA18.Z' interrupted, exit status: c0000094
BR0272E Execution of program 'D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\mkszip -c D:\ORACLE\PRD\SAPDATA4\SR3700_18\SR3700.DATA18 > F:\PRDBACKUP\bdyjmnib\SR3700.DATA18.Z' through pipe failed
BR0224E Compressing D:\ORACLE\PRD\SAPDATA4\SR3700_18\SR3700.DATA18 to F:\PRDBACKUP\bdyjmnib\SR3700.DATA18.Z failed due to previous errors
BR0280I BRBACKUP time stamp: 2008-07-17 02.58.45
BR0317I 'Alter tablespace PSAPSR3700 end backup' successful
BR0115I Compression rate for all files 6.0128:1
BR0056I End of database backup: bdyjmnib.and 2008-07-17 02.58.41
BR0280I BRBACKUP time stamp: 2008-07-17 02.58.46
BR0054I BRBACKUP terminated with errors
thanks in advance.thnks for prompt reply Juan,
parameters for init<sid>.sap files for compression are as follows:
compress_cmd = "D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\mkszip -c $ > $"
uncompress command
first $-character is replaced by the source file name
second $-character is replaced by the target file name
<source_file_name> = <target_file_name>.Z
for uncompress command the -c option must be set
no default
uncompress_cmd = "D:\usr\sap\PRD\SYS\exe\uc\NTAMD64\uncompress -c $ > $"
directory for compression [<path_name> | (<path_name_list>)]
default: value of the backup_root_dir parameter
compress_dir = D:\oracle\PRD\sapreorg
brarchive function [save | second_copy | double_save | save_delete
| second_copy_delete | double_save_delete | copy_save
| copy_delete_save | delete_saved | delete_copied]
default: save
compress dir is on D drive, where space is available.Shall i give you a whole parameters for this file? -
0MATERIAL and 0CUSTOMER Delta error
Hi Gurus,
I have a problem regarding the 0MATERIAL and 0CUSTOMER Delta. It stopped due to an error in source system. When I tried to do a Repeat Delta, the system did not permit me because the Infosources does not allow update mode R (repeat). I checked previous SDN topics and found the solution.
1. Delete 'Delta Init' in Delta Channel (InfoPackage)
2. Do a Init load.
My questions are:
1. Is this the proper process or did I misinterpret the posts.
2. Would creating a new Init for the InfoSource not affect the data in the Cubes?
3. Do I have to create a Delta right after the Init?
Please advise,
JakeHi Jake,
1. Is this the proper process or did I misinterpret the posts.
>>Solution suggested by you is fine,
2. Would creating a new Init for the InfoSource not affect the data in the Cubes?
>> It should not affect the cube data, remember to activate your master data ( customer & material) after data load ( right click -->activate)
3. Do I have to create a Delta right after the Init?
>> you need to create delta Infopackage whenever you wish to take delta from R/3. When you do the intialization system starts tracking delta for you irrespective of whether you create delta infopackage in BW or not.
hope it helps
regards
VC
Message was edited by: VC -
Hi All,
I installed the 0SD_C01 and did the init delta without data transfer. In R3, when I try data extractor RSA3 for 2lis_01_s001 it extracts 0 records. Also when I try delta load as soon as I do init without data transfer, I get an error. Does this mean I have no data in R3 or something wrong with my delta extraction.
In the monitor I see 'Caller 09 contains an error message'
Further analysis says 'Error in SOurce System'
But I see no errors in SM37, ST22 or ST21 in R3.
Please Help.
Thanks,
Arthur.Hi Arthur,
As you are using the old LIS Structures,
First you have a look at communication tables MCVBAK MCVBAP and so on .Then have a look at 2 tables and One Infostructure,
they are XXXXSBIW1 , XXXXSBIW2 , XXXXSBIWS.
These are transparent tables , BIWS is extract Structure and other two are data tables . u can check the active status of data transfer table in the TABLE TMCBIW
Check in Transaction MC23 and check for the Update Rules, they all should be active .
u can maintain Updating in LBW1 trasaction.
Hope it helps.
Thanks,
krish
*Awarding Points is a way of Saying thanks in SDN -
0FI_GL_10 can't delta :Errors occurred during the extraction.
hi,sdn!
i have 3 DataSources,
0FI_AA_11(FI-AA: Transactions),
0FI_AA_12(FI-AA: Posted Depreciations) and 0FI_GL_10(General Ledger: Leading Ledger Balances).
The initialize and full extraction is ok.
when i delta it in rsa3,the system tell me:Errors occurred during the extraction.
Is Append Structure result in this error?
i want to know the reason,thanks!For summarization of line items by master record characteristics (such as cost center) during posting of ODS objects to InfoCubes, master data must already exist prior to extraction of transaction data. The following sequence must therefore be kept to during extraction:
0FI_GL_4
General Ledger: line items (if required)
0ASSET_ATTR_TEXT
Asset subnumber (flexible updating)
0ASSET_AFAB
Depreciation area real or derived
then the transaction data
0FI_AA_11
FIAA : transactions and / or
0FI_AA_12
Posted depreciations (period values) -
Hi,
While loading delta, i got an error.
Record 3873 :InfoObject /BIC/ZWEMPF does not contain alpa-conforming value 092
Record 3874 :InfoObject /BIC/ZWEMPF does not contain alpa-conforming value 092
can anybody can explain what it means.
how to rectify this error.
delta was loaded into PSA but not loaded into ODS.Hi Rajini,
This ios because the request which is being loaded from PSa to DSo contains some invalid data in the field mentined.
1)go to PSA right click - > manage.
2)select the request and click on display data.
3)go to the record numbers mentioned and check the field ZWEMPF of the records for invalid data.
4)correct this records. and save data.
5)delete the red request from DSO.
6)run the delta DTP again.
Hope this helps.
Cheers,
Srinath. -
Communication error CPIC return code 019 SAP return code 728. Delta error
Hello Experts,
Would just like to ask if what we suspect is correct. We have running deltas in process chains occurring every early morning. However, upon checking the delta that should have run today, I found that the delta did not push through. I only found this one dump in SM21 that I think is related to the issue:
MNo.
R49 Communication error, CPIC return code 019, SAP return code 728
R5A > Conversation ID: 61442686
R49 Communication error, CPIC return code 019, SAP return code 728
R64 > CPI-C function: CMSEND(SAP)
R5A > Conversation ID: 61443687
R64 > CPI-C function: CMSEND(SAP)
R49 Communication error, CPIC return code 019, SAP return code 728
R5A > Conversation ID: 61444687
R64 > CPI-C function: CMSEND(SAP)
Now we think that the delta did not push through because we are encountering issues with regards to our SAP R/3 system (the source system) and it is currently inaccessible. Did the delta not push through because of the issues and inaccessibility/uber slow processing of our SAP R/3 server? And is the error specified above illustrating this? Any explanation would help. I have already tried looking for similar issues but cannot find anything. Please help. Thanks!Hi
As far I know, The SAP Gateway carries out CPI-C services within the SAP world, which are based on TCP/IP. These services enable SAP Systems and external programs to communicate with one another.
CPI-C services can be used either in the ABAP program or for the external programs via the interfaces.
As RFC (remote function call) is based on CPI-C, all RFC connections also pass through the SAP Gateway.
Errors When Starting Remote Programs Using Remote Shell
When you use remote shell to start CPIC programs on other hosts, the following conditions apply:
The (gateway) UNIX ID must be available on the other host
The gateway host must be entered in the remote host in the file ".rhosts". This file must be located in the HOME directory of the (gateway) UNIX ID.
The program you want to start must be installed in the HOME directory of the (gateway) UNIX ID on the remote host.
Read more from help
http://help.sap.com/saphelp_nw04s/helpdata/en/99/5f8c0bcb7d4280aa862254cffceada/frameset.htm -
Runtime error in PRD but working in DEV.
Hi,
my application is running fine in DEV but a runtime exception occurs in PRD.
com.sap.tc.webdynpro.progmodel.context.ContextConfigurationException: DataNodeInfo(Emporgcust.Zhr_All_Reportees_Input.Output.It_Disp11): structure field Emp_Desig not found
at com.sap.tc.webdynpro.progmodel.context.DataAttributeInfo.init(DataAttributeInfo.java:299)
at com.sap.tc.webdynpro.progmodel.context.NodeInfo.initUnmappedAttributes(NodeInfo.java:687)
at com.sap.tc.webdynpro.progmodel.context.DataNodeInfo.doInit(DataNodeInfo.java:238)
at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:671)
at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:674)
BAPI is there in PRD & working fine.
Regards,
AmitHi,
If structure field "Emp_Desig" is newly added then this is the problem with metadata cache issue.
Try invalidating the metadata chache using the below document:
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/10465350-b4f5-2910-61ba-a58282b3b6df
Or else the final solution is:
Restart Portal Server
See the below thread also for these kind of meta data chache issues:
Re: ArrayIndexOutofBoundsException
Regards,
Charan -
EXTACTOR 2LIS_02_SCL DELTA ERROR REMNG REWRT /WEMNG /WEWRT
Hi,
I add the following fields REMNG /REWRT/ WEMNG /WEWRT in the LO cockpit
but do not understand the delta behavior.
When i extract a Invoice receipt in delta : (0processkey = 3).
fields REMNG /REWRT are OK but REMNG /REWRT are set to 0 and
infoobject are overwritten in the ODS.
When i extract a good receipt in delta : (0processkey = 2)
REMNG /REWRT are set to 0.
I do not understand how good receipt key figure and invoice receipt key figure 0GR_VAL 0 INV_RC_VAL can be correctly populate in delta mode with 2LIS_02_SCL ?
thanks for your helpHi,
the scl-extractor for purchase delivers the granualrity Schedule line.
But in Purchase, with respect to a schedule line, you can have various things happenig. As youve described: Goods receipt, invoices and so on ...
As far as I know it's only possible to use the scl-extractor in additive mode. This is beause the fields that are delivering the required values deliver only the values of the latest event that has taken place (invoice OR goods receipt).
So if oyu use an ODS in overwrite-mode, the old, proper values are overwritten by the values of the latest record, coming via 02_scl.
One option is, to enhance the Extractor with the document-number an FI-Document-Number and add these fields as well to the ODS (overwrite).
This should work. But then you must make sure that, when initialising, you split up the cummulative record for the init into the several records provided by the document flow in pruchase.
To cut it short: chage the update-rules to "additive" on the way to your ODS.
sorry.
hth
cheers
Sven -
My recent delta from R/3 for a customer showed his street address and REGION being changed , however R/3 shows the change occured last september.
Info Object - 0CUSTOMER
Data source is Delta
Any ideas....
All teh deltas are running fine, in fact we did a full/init recently and deltas all doing good.
Any help in this is appreciated.Hi Gopikrishna,
We had a similar issue recently when soem records that should have been in a delta load 4 months back, suddenly were loaded to BW. The issue was caught due to a date we maintain in the data and the sequence messed up the data (this was a transactional load). The reason turned out to be that the IDocs for this load were "stuck" on R/3 since Feb and another job that is supposed to process all 'hanging' IDocs was executed.
But as your situation is with master data, I guess it would not be a problem... -
Hi,,,
we are updating one cube through DSO during last delta its showing reuest to be red n wen we see the monitor screen its showing yellow.... plz let me know what steps shud be taken to repeat delta at DSO itself .
urgent
help wud b appreciatedChk for any jobs in SM37 or any background process related to the load in SM66 or SM50. In datatarget if the load is running for long time it might change to red..that doesnt mean the laod has failed. Chk for any hanged IDOCS in sm58.
Regards,
B -
hi experts,
if delta load fails b/n ods &infocube
how to rectify that , for that what is the procedure
when we are loading the data ods to infocube how to choose the
keyfields?is it equal to dimensions
thanks in advance
venuHi,
It's the same procedure which we follow for the delta from R/3 to the Bw targets.
The only thing is if you can correct it in the PSA then you can correct it there and then load it from there.
Or you can delete the failed delta request from the cube and relaod the delta
it will give you warning that you are repeating the delta.the new delta will bring the records from the failed delta as well as the records from the new delta if any.
Th key fields of the ODS are not equivalent to dimension.
Dimension are for the logical groupings of the objects and are decided in such a way that the size of dimension table should bve as small as possible.
Where as the key fields of the ODS are like the keys of the table if you want to identify a particular value with respect to a char or combination of char.just imagine it as a table with keys.
hope it clears
Thanks -
Please help!! K7N2 Delta error
Today I was playing a game but instantly my monitor shutted down. X( I turned off the power and then back on, but my system hung again :( (monitor didn't get any signal). I had a look in back of my computer and saw some D-Bracket2 lights (1,4 red 2,3 green). Manual says that they means "Processor initilization" or something like that ?( and system hangs right there. Does this mean that my mobo is gone broken? :(
Specs.
K7N2 Delta L
Athlon XP 2600+ on stock
512MB PC2700
Geforce 4 Ti4200 64MB (OC 300/550mhz)My power supply is 300W thank you for asking, and my ram brand seems to be spectek, why? Isn't that ok? I tried just what you said (clear cmos) but nothing. :( Should the power be turned on or off when you switch the jumpers? ?(
I also found something very iteresting. When i leave the fbs 100/133 jumper open, the D-Bracket complains that my memory is damaged. 8o What does that mean?
Maybe you are looking for
-
Stock Report for Individual Stock Segments
Is there a report similar to MCBZ, but very specifically showing individual stock segments like sales order stock?
-
FB 4.5 crash in windows 7 after today update
Hi all, After updating windows 7 update my FB 4.6 stop working. I found this error on a log file: # A fatal error has been detected by the Java Runtime Environment: # EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x0018e24e, pid=4624, tid=1336 # JRE
-
I am writing a calc script for Hyperion Planning 11.1.1.2 that will calculate new maintenance revenue for 15 months based on on accumulation of license revenue with a 60 day delay. A simple example is: Year 1 Jan = 0 Feb = 0 Mar = Jan * rate Apr = Ja
-
Naming conventions to store automation testing scripts
Hi, Can anyone provide the solution for Naming conventions to store automation testing scripts in oracle application testing suite? Regards, Sairam
-
Combine the 3 BW systems Into new BW System
Hi Frds, Thee are 3 BW/BI systems in my company for some years. Now we plan to combine the 3 BW systems into new BI System. for exp we have A, B , C BW systems( each system having BW 3.X And BI7.0 Objects) and each system having diffrent kind of Sour