Vision suite OMS400/ODS400

[Former Member]

Hi all,

Has anyone among you been using OMS400/ODS400 for replication to a alternate site for SAP?

How good is the product as compared to MIMIX HA Lite..MIMIX suite of products?

Am asking this question as at my current workplace, they are using OMS400/ODS400 to replicate SAP.

They were using OMS400/ODS400 to replicate their old legacy system earlier and when they switched to SAP, they continued to use OMS/ODS...

Since the beginning of the implementation we have faced problems replicating REPLOAD/REPOSRC to the alternate site. These files always go in a "HELD"(inactive status) on the target side...

Now this product has something called a CRC check, which run and repairs the file if anything is missing..

But that's all they have..They do a SYNC check and a CRC check and if it comes out fine, they think its the same on the target and source.

They(OMS/ODS) do not do checks like in MIMIX HA lite : File Data, File Entry in the data group, file attribute and file attribute member check etc....which I think are a lot more checks ...

Now yesterday, even though all the CRC check passed before we rolled over to the alternate site, we could not log on to the system.

Firstly, when we rolled over, there was no SAP kernel..somehow the OMS400/ODS400 product has wiped the kernel library..so we applied the kernel, deleted any SQL packages, if any, to start the system...not sure why?? and it a big question mark...

The SAP system started, but then the log screen has a runtime error..."Program SAPMSSYD either has a length of 0 or does not exist"...

The Work process trace file showed this continously...

A ABAP Program ????????????????????????????????????????.

A Source Line 0.

A Error Code LOAD_ZERO_SIZE.

A Module $Id: //bas/700_REL/src/krn/runt/abload5.c#3 $ SAP.

A Function db_open Line 393.

A ** RABAX: level LEV_RX_STDERR completed.

A ** RABAX: level LEV_RX_RFC_ERROR entered.

A ** RABAX: level LEV_RX_RFC_ERROR completed.

A ** RABAX: level LEV_RX_RFC_CLOSE entered.

A ** RABAX: level LEV_RX_RFC_CLOSE completed.

A ** RABAX: level LEV_RX_IMC_ERROR entered.

A ** RABAX: level LEV_RX_IMC_ERROR completed.

A ** RABAX: level LEV_RX_DATASET_CLOSE entered.

A ** RABAX: level LEV_RX_DATASET_CLOSE completed.

A ** RABAX: level LEV_RX_DATASET_CLOSE completed.

A ** RABAX: level LEV_RX_RESET_SHMLOCKS entered.

A ** RABAX: level LEV_RX_RESET_SHMLOCKS completed.

A ** RABAX: level LEV_RX_ERROR_SAVE entered.

A ** RABAX: level LEV_RX_ERROR_SAVE completed.

A ** RABAX: level LEV_RX_ERROR_TPDA entered.

A ** RABAX: level LEV_RX_ERROR_TPDA completed.

A ** RABAX: level LEV_RX_PXA_RELEASE_RUDI entered.

A ** RABAX: level LEV_RX_PXA_RELEASE_RUDI completed.

A ** RABAX: level LEV_RX_LIVE_CACHE_CLEANUP entered.

A ** RABAX: level LEV_RX_LIVE_CACHE_CLEANUP completed.

A ** RABAX: level LEV_RX_END entered.

A ** RABAX: level LEV_RX_END completed.

A ** RABAX: end no http/smtp

A ** RABAX: end RX_BTCHLOG|RX_VBLOG

A ** RABAX: end RX_BTCHLOG|RX_VBLOG

A Program SAPMSSY2 either has a length of 0 or does not exist..

A

M *** WARNING => PfStatWrite: missing STAT_END for opcode STAT_REPLOAD [pfxxsta

B

B Sat Nov 22 19:39:07 2008

B 202 seconds passed since last buffsync

A

A Sat Nov 22 19:40:08 2008

A TH VERBOSE LEVEL FULL

A ** RABAX: level LEV_RX_PXA_RELEASE_MTX entered.

A ** RABAX: level LEV_RX_PXA_RELEASE_MTX completed.

A ** RABAX: level LEV_RX_COVERAGE_ANALYSER entered.

A ** RABAX: level LEV_RX_COVERAGE_ANALYSER completed.

A ** RABAX: level LEV_RX_ROLLBACK entered.

A ** RABAX: level LEV_RX_ROLLBACK entered.

A ** RABAX: level LEV_RX_ROLLBACK completed.

A ** RABAX: level LEV_RX_DB_ALIVE entered.

A ** RABAX: level LEV_RX_DB_ALIVE completed.

A ** RABAX: level LEV_RX_HOOKS entered.

A ** RABAX: level LEV_RX_HOOKS completed.

A ** RABAX: level LEV_RX_STANDARD entered.

A ** RABAX: level LEV_RX_STANDARD completed.

A ** RABAX: level LEV_RX_STOR_VALUES entered.

A ** RABAX: level LEV_RX_STOR_VALUES completed.

A ** RABAX: level LEV_RX_C_STACK entered.

A ** RABAX: level LEV_RX_C_STACK completed.

A ** RABAX: level LEV_RX_MEMO_CHECK entered.

A ** RABAX: level LEV_RX_MEMO_CHECK completed.

A ** RABAX: level LEV_RX_AFTER_MEMO_CHECK entered.

A ** RABAX: level LEV_RX_AFTER_MEMO_CHECK entered.

A ** RABAX: level LEV_RX_AFTER_MEMO_CHECK completed.

A ** RABAX: level LEV_RX_INTERFACES entered.

A ** RABAX: level LEV_RX_INTERFACES completed.

A ** RABAX: level LEV_RX_GET_MESS entered.

A ** RABAX: level LEV_RX_GET_MESS completed.

A ** RABAX: level LEV_RX_INIT_SNAP entered.

A ** RABAX: level LEV_RX_INIT_SNAP completed.

A ** RABAX: level LEV_RX_WRITE_SYSLOG entered.

A ** RABAX: level LEV_RX_WRITE_SYSLOG completed.

A ** RABAX: level LEV_RX_WRITE_SNAP entered.

A ** RABAX: level LEV_SN_END completed.

A ** RABAX: level LEV_RX_SET_ALERT entered.

A ** RABAX: level LEV_RX_SET_ALERT completed.

A ** RABAX: level LEV_RX_COMMIT entered.

A ** RABAX: level LEV_RX_COMMIT entered.

A ** RABAX: level LEV_RX_COMMIT completed.

A ** RABAX: level LEV_RX_SNAP_SYSLOG entered.

A ** RABAX: level LEV_RX_SNAP_SYSLOG completed.

A ** RABAX: level LEV_RX_RESET_PROGS entered.

A ** RABAX: level LEV_RX_RESET_PROGS completed.

A ** RABAX: level LEV_RX_STDERR entered.

A Sat Nov 22 19:40:08 2008

A

A ABAP Program ????????????????????????????????????????.

A Source Line 0.

A Error Code LOAD_ZERO_SIZE.

A Module $Id: //bas/700_REL/src/krn/runt/abload5.c#3 $ SAP.

A Function db_open Line 393.

A ** RABAX: level LEV_RX_STDERR completed.

:

:

:

:

We finally decided to abort the failover test and go back to the original source...

and gues what...now the original kernel on the original source is wiped out...Same issue we had on the target...Reapplied the kernel and

and restarted SAP..everything looked allright luckily...Nothing had replicated back from the target to the original source to make things messy...:))

Now when we logged on to the original source, we saw hundreds of ABAP dump :Runtime Errors LOAD_ZERO_SIZE

The Error analysis show this:

What happened?

Error in the SAP kernel.

The current ABAP "????????????????????????????????????????" program had to be

terminated because the

ABAP processor detected an internal system error.

Error analysis

Database inconsistency: program "RSPOWP00" is described in the table

REPOLOAD but when the data was accessed it could not be

found or the data had the length 0.

Now we are having serious concerns about the integrity of the Data which we are replicating across to the alternate site using OMS/ODS...If there is data missing in REPLOAD/REPOSRC..then what else is missing, we do not know...and am kind of nervous with OMS/ODS...

Have seen MIMIX and woked with HA Lite

...But just wanted to let you know all and see if some one has any ideas about OMS/ODS400....and how good/bad with SAP replication??

Thank you in advance for your suggestions/ideas...

Abhi

[Former Member · Accepted solution]

Hello Abhi,

I use OMS400/ODS400 to replicate our SAP R/3 system with HA remote server.

Our experience is bad, i have some inactives objects without any reasons; when i execute a SYNCHECK this process shows some objects inactives.

Our local support recommend ITERA or MIMIX HA solution.

Regards,

Ernesto Castro.

[Former Member · Accepted solution]

Hi Ernesto

Thanks for the reply...

We are in discussions with vision support, but I am not sure if I have the confidence left in the product to plan a role swap....after seeinng what happened with our earlier switch test..

Have you performed a role swap from the source to the target successfully with OMS400/ODS400 for SAP?

I am not even sure as to how many customers on i5 running SAP have OMS400/ODS400 who have switched...

vision support was not even confirming how many customers they have who are running OMS/ODS with SAP running...so am kinda nervous...

Thanks in advance for your comments

Abhi

[Former Member · Accepted solution]

Hello Abhi.

Yes, i make a roll swap with Orion and R/3 4.6C two years ago and this work fine.

now i change from local to remote journal configuration ( 4 months ago) and the replication work very good, the inactive´s objects issues dissapear and the performance is better.

Regards,

Ernesto Castro

[Former Member]

Please call the Vision CustomerCare organization, (800) 337-8214 (North America) or +1 949 724-5465, regarding your issue with the missing Kernel during your switchover test.

Ask them to open a Service Record regarding your issue and have them ask that I assist you. We need to look at your ODS selection rules.

You may be selecting the symbolic link for the kernel which is not advisable. I have written a document to illustrate the appropriate IFS selection rules for the SAP application with ORION.

Regards,

Frederick L Grunewald

Sr. Solutions Engineer

Vision Solutions, Inc.

[Former Member]

Hi, I'm getting same error: LOAD_ZERO_SIZE

Can you tell me which was the solution for this issue?

Ximo Escobedo, SAP Basis Consultant

[Former Member]

Hi Ximo

The Solution was to replace the product all together...with MIMX...

They have some product issues in ODS/OMS400 while trying to replicate BLOB objects...The Architect was on the issue, and we gave them time after time and finally changed the product...

They may have revised and redesigned the product in the meanwhile..so I am not sure...I am talking six months back in time...

This issue i guess started with ECC 5.0/6.0...only... with earlier relases...4.6C and so on it used toi be ok...

Hope that helps...

Thanks

[Former Member]

All I can say is swicth back to the main instane ASAP...

u do not want replication in the reverse direction or your only solution will be a restore... )

Thanks

Abhi

[Former Member]

Thank you very much for your replies, Abhi

Ximo Escobedo, SAP Basis Consultant

[Former Member]

Hallo Everybody,

SAP Note No. 1426367 has been prodced in response to this issue after consultation with Vision (thank you, Fred!).

Regards,

Sally Power

SAP Development Support for SAP on IBM i

[Former Member]

Hi,

Sorry for the delay in answering. We have been using OMS400/ODS400 for about 6 year now and role-swap every few months without any issues. The source and target systems have differnet names and therefore we exclude certain configuration tables and IFS entries from the mirroring process.

As part of the original setup we used a document/white papaer from Vision that details the setup to be used with SAP.

We have not seen any of the errors you have indicated and we do not get any tables going out os sync. However we are only using the SAP/HR module and are currently running 4.6C

We are due to perform a CPC conversion soon and then will move on to ECC 6.0 which might be a completely differnet story.