You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 12 Next »

Connection with UD CONNECT

Dynasys is a MSSQL tool, BW WBP is on an AIX server. No ODBC driver exists between BW and MSSQL server in Linux / AIX.

This problem was solved setting an UD connect connection

User ID for Dynasys connection is Dynasys_Interface / Password  : 791hB6zi8Rk1DBSV3uNG  (Prod/Tst/Dev)

Main servers:

Dynasys Development server => wdcslvbd31\slv1_dbdev  => connected to WBD
Dynasys Testing server => wdcslvbt31\slv1_dbtst => connected to WBQ
Dynasys Production server => wdcdyap21\dy_dbprd => connected to WBP


Previous one (update given by Abdelmôti 2019/03/22)

  • Dynasys Production server: WDCCLSLVBP01\SLV1_DBPRD => connected to WBP
  • Dynasys Testing server: WDCCLSLVBV01\SLV1_DBTST => connected to WBQ
  • Dynasys Development server: WDCSLVBD11\SLV1_DBDEV  => connected to WBD

Important:

  • Adagio Team is in charge of UD Connect connexions. Admin Change to be created by Guillaume T for any change or issue.
  • Wintel Operations is in charge of DynaSys servers (Contact Abdelmôti KHABABA)

Known Issues

Field XXX is not a member of XXX

 

 

This is a known problem that has already been encountered. Some explanation in the following sapnote: https://launchpad.support.sap.com/#/notes/1007409

This is linked to the datasource structure being cached in J2EE layer when using preview functionnality.

Solution:

WBP Production issue : cache to clear on BPJ

WBQ Quality issue : cache to clear on BQJ

WBD Development issue : cache to clear on BDJ


For WBD/WBQ, email Adagio team

For WBP, ask Laure Pichot to create an RFC and email IBM (slvhd@be.ibm.com) + Adagio (is-adagio-sap-operations@solvay.com) with following information :

Title : URGENT - RFC 70000xxxxx - Need to clear JCO metadata caches on BPJ

Mail : 
"We are about to move BW evolutions on WBP.
We need you to clear ones JCO metadata caches for BPJ now. Operation has to be done by 6pm CET today.

It concerns structure /BIC/CADTS_EXP 0000300000001".

PS : the structure name must not contain any space

Column XXX not found

The field Name has to be up to 30c maximum

The field Name in DataSource has to be 16c maximum

 

Solution:

Ask DynaSys team to respect limits :

=> Table or View Name has to be up to 16c maximum

=> The field Name can be up to 30c but has to be unique on 16 first characters

=> new fields have to be added at the end of table otherwise transports to production have to be closely synchronized.




  • No labels