Distributed Database + DB13 + SAPXPG + Standalone Gateway

Hi All,
I knew this question has been asked and answered but i still couldn't find the concrete solution. Any advise is mostly welcome.
I've installed Distributed Database on Solaris and CI on Solaris as well. Due to security reason and policies, our customer stop us from using RSH.
I've installed standalone gateway in Distributed Database with System Name EGW, system number 20. My SAP and DB name is AEP.
gwrd is started using egwadm. TCP_IP connection SAPXPG_DBDEST_DBHOSTNAME works fine, however when i kick off checkDB in DB13, i got the below error:
"> Function: BtcXpgPanicCan't exec external program (No such file or directory)"
Have i miss out something? Do i need to add any ENV to egwadm or edit the SAPXPG program?
fyi, br* and SAPXPG authorization are all set correctly in /sapmnt/AEP/exe. Env for AEPadm in CI is identical to AEPadm in DB server.
Please advise.
Thanks,
Nicholas Chang.

Hi All,
Since there's no SAP Note explaining how to setup standalone gateway in UNIX env and incorporate for brtools to work in distribtuted system. I'll summarize the resolution here:
1) Install GW in database server
2) update the GW start profile with below value:
BGW = Gateway's SID.
SETENV_00 = LD_LIBRARY_PATH=$(DIR_LIBRARY):%(LD_LIBRARY_PATH)
SETENV_01 = SHLIB_PATH=$(DIR_LIBRARY):%(SHLIB_PATH)
SETENV_02 = LIBPATH=$(DIR_LIBRARY):%(LIBPATH)
SETENV_03 = ORACLE_SID=SID
SETENV_04 = SAPDATA_HOME=/oracle/
SIDSETENV_05 = PATH=$PATH:/home/BGWadm:/usr/sap/SID/SYS/exe/run:/usr/bin:.:/usr/ccs/bin:/usr/ucb:/oracle/SID/112_64/bin
3) update BGWadm env profile - sapenv_HOSTNAME.csh
setenv SAPDATA_HOME /oracle/SID
setenv ORACLE_SID   SID
setenv PATH /home/bgw:/usr/sap/BGW/SYS/exe/run:/usr/bin:.:/usr/ccs/bin:/usr/ucb:/oracle/SID112_64/bin
setenv ORACLE_HOME /oracle/SID/112_64
setenv USER bgwadm
setenv dbs_ora_schema SAPSR3
setenv NLS_LANG AMERICAN_AMERICA.UTF8
setenv DB_SID SID
setenv dbs_ora_tnsname SID
setenv dbms_type ORA
setenv LD_LIBRARY_PATH /usr/sap/SID/SYS/exe/run:/oracle/SID/112_64/lib
setenv DIR_LIBRARY /usr/sap/SID/SYS/exe/run
4) copy br* to gateway's /sapmnt/SID/exe/ and ensure 4775 is granted
5)Create the special OPS$ setting to allow BGWADM to log into the database.  use the script below .  Log in as oraSID to run this on DB host via SQLPLUS (connect /as sysdba)
CREATE USER "OPS$BGWADM" DEFAULT TABLESPACE PSAPSR3USR
TEMPORARY TABLESPACE PSAPTEMP IDENTIFIED EXTERNALLY;
grant unlimited tablespace to "OPS$EGWADM" with admin option;
grant connect to "OPS$BGWADM" with admin option;
grant resource to "OPS$BGWADM" with admin option;
grant connect to "OPS$BGWADM" with admin option;
grant resource to "OPS$BGWADM" with admin option;
grant sapdba   to "OPS$BGWADM" with admin option;
CREATE TABLE "OPS$BGWADM".SAPUSER
(USERID VARCHAR2(256), PASSWD VARCHAR2(256));
INSERT INTO "OPS$BGWADM".SAPUSER VALUES ('SAPSR3',
'your_password');
6) stop gateway and kill gateway sapstartsrv
7) start gateway
8) in CI - SM59 - TCP_IP -> SAPXPG_HOSTNAME_DB -> ensure gateway host is points to DB server and sapgw is the system number for DB Gateway
9) test checkDB in db13.
Cheers,
Thanks,
nicholas chang.

Similar Messages

  • Problem in DB13 - standalone gateway installed - error due to env

    Hello,
    As we have db and ci on separate server and there was no gateway on db server, I installed standalone gateway the rfc connection started working fine. When I try to execute any BR* command through DB13, it gives error.
    I checked using SM69 the output of env and BRTOOLS using the working RFC destination.
    BRTOOLS ends with return code 3 - BR0152E Environment variable ORACLE_SID is not set
    I modified .sapenv.csh and .sapenv.sh in /home/sidadm of gateway sid, but the error remained the same.
    When command env is run through SM69 suing the working RFC destination, its output is not having the set variable values.
    In trace, there are no errors reported, but it does not show which environment variable file its checking.
    Can someone please let me know which environment variable file is checked when the SM69 - env is run?
    Thank you,
    Vaibhav

    Dear Vaibhav,
    Please,check the environment variable using the transaction SM49
    and external command "ENV" for Unix - this is the environment valid
    for jobs running from DB13. The environment of ora<sid> on Unix is not
    relevent for jobs running from DB13.
    1. please copy appropriate version of BR*-executables in the directory
    /sapmnt/SID/exe and set the owner and permissions as per note #113747.
    2. set the environment variables ORACLE_SID, ORACLE_HOME, SAPDATA_HOME,
    SAPSID=SIDfor the user "sidadm" and restart the standalone gateway
    to activate the new environment.
    After that changes, DB13 jobs should work.
    Regards,
    Rafael

  • Tips before installing a Standalone Gateway on MSCS

    Hi there,
    I have installed an ECC system running on MSCS already but in order to use DB13 transaction properly I´m planning to install a Standalone Gateway in the database server. Apart of SAP note 657999 or installation guides there´s anything to pay special attention before doing this ?
    I highly appreciated your comments.
    Best regards,
    Everton

    Hi Mark,
    Thank you for your time !
    Best,
    Everton

  • Stats from Standalone Gateway in ST03

    Per SAP recommendation, I have installed a standalone gateway for my MSCS cluster.  SAP recommended this so that the database statistics would showup in the EarlyWatch reports and ST03.  I had created the Standalone gateway per note 657999 and I am wondering how I can add these stats in ST03.

    Hi,
    I think the standalone gateway installation for MSCS is mainly to be able to use transactions ST04, OS07 (equivalent of ST06 where you can choose the database RFC destination) and brtools from transaction DB13.
    In ST03, I've got exactly the same information as if we were not using MSCS.
    It works great on my MSCS R/3 4.7 system.
    Regards,
    Olivier

  • Best Practice for Distributing Databases to Customers

    I did a little searching and was surprised to not find a best practice document for how to distribute Microsoft SQL Databases. With other database formats, it's common to distribute them as scripts. It seems that feature is rather limited with the built-in
    tools Microsoft provides. There appear to be limits to the length of the script. We're looking to distribute a database several GBs in size. We could detach the database or provide a backup, but that has its own disadvantages by limiting what versions
    of the SQL Server will accept the database.
    What do you recommend and can you point me to some documentation that handles this practice?
    Thank you.

    Its much easier to distribute schema/data from an older version to a newer one than the other way around. Nearly all SQL Server deployment features supports database version upgrade, and these include the "Copy Database" wizard, BACKUP/RESTORE,
    detach/attach, script generation, Microsoft Sync framework, and a few others.
    EVEN if you just want to distribute schemas, you may want to distribute the entire database, and then truncate the tables to purge data.
    Backing up and restoring your database is by far the most RELIABLE method of distributing it, but it may not be pratical in some cases because you'll need to generate a new backup every time a schema change occurs, but not if you already have an automated
    backup/maintenance routine in your environment.
    As an alternative, you can Copy Database functionality in SSMS, although it may present itself unstable in some situations, specially if you are distributing across multiple subnets and/or domains. It will also require you to purge data if/when applicable.
    Another option is to detach your database, copy its files, and then attach them in both the source and destination instances. It will generate downtime for your detached databases, so there are better methods for distribution available.
    And then there is the previously mentioned method of generating scripts for schema, and then using an INSERT statement or the import data wizard available in SSMS (which is very practical and implements a SSIS package internally that can be saved for repeated
    executions). Works fine, not as practical as the other options, but is the best way for distributing databases when their version is being downgraded.
    With all this said, there is no "best practice" for this. There are multiple features, each offering their own advantages and downfalls which allow them to align to different business requirements.

  • Standalone Gateway in MSCS not working correctly

    Dear Experts,
    I have installed a standalone gateway according to note 657999 in a BW cluster system. I already installed 2 standalone gateways in 2 other systems and they are working fine. I am checking this using sm49 and running a zdir external program in each node.
    Although the services were installed and started correctly, as well as the GW cluster resource, external programs still run only in one node and fail when run from the other node.
    Any thoughts will be pointly appreciated. Thank you.

    I have bought Adobe Acrobat X Standard & now works

  • Exchange 2010 Trying to Deleting Database Mailbox(DB13), error database "DB13" has multiple copies on other servers. Must remove all copies from other servers

    Help, not sure how to proceed via Powershell or EMC.
    Thanks!!

    Hi,
    Please use this command to check the status information for copy of database “DB13”
    Get-MailboxDatabaseCopyStatus -Identity DB13
    In the name field, we will know the copy stays on which server. Then use the following command to remove these copies.
    Remove-MailboxDatabaseCopy -Identity DB13\MBX -Confirm:$False
    Use the EMC to remove a mailbox database copy:
    In the console tree, navigate to Organization Configuration > Mailbox.
    In the result pane, on the Database Management tab, select the mailbox database whose copy you want to remove.
    In the work pane, on the Database Copies tab, right-click
    the database copy that you want to remove, and then click Remove.
    Click Yes to remove the database copy.
    After removing these database copies, then try to delete this mailbox database.
    Best Regards.

  • Standalone Gateway configuration

    I installed Standalone gateway for our CRM server. How to connect standalone gateway with central instance?
    Gateway Host: SAPTST
    SID: CSD
    Instance number: 03
    Central instance: SAPCRM
    SID: CRD
    Instance Number: 01
    Thanks
    Reddy

    Hi Reddy,
    what do you want to do with the stand alone gateway? Stand alone gateways are in general used for example 3rd party products which do run on machines where there is no SAP Based System installed. Lets say you do have a 3rd party product wich supports the connection via RFC from SAP Systems. You can then connect the 3rd party application to this standalone gateway. Once this is done you can then go to transaction SM59 and set up a TCP/IP connection to the 3rd party product and use the gateway installed on the 3rd party machine.
    This is just a very general explanation of what you can do with a standalone gateway. There are some other options but to go into more detail you need to explain a little more what you want to do.
    regards Ingo

  • Distributed database

    Hi Everyone,
    We are looking at different options to connect the forte application to
    distributed database.
    Any help greatly appreciated
    Thanks & Regards
    Raju
    (Pothuraju Katta)
    [email protected]
    Phone: 847-969-3000
    Fax: 847-995-8287
    To unsubscribe, email '[email protected]' with
    'unsubscribe forte-users' as the body of the message.
    Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>

    Hi Haidar,
    Actually, SQL Server does not recognize "distributed database" as concept.
    Based on your description, you want to access databases located at different locations. To achieve the requirement, you can create
    linked servers
     or configure
    replication in SQL Server.
    Linked servers provide SQL Server the ability to access data from remote data sources. Using these mechanisms, you can issue queries, perform data modifications and execute remote procedures.
    Replication is a set of technologies for copying and distributing data and database objects from one database to another and then synchronizing between databases to maintain consistency. Using replication, you can distribute data to different locations and
    to remote or mobile users over local and wide area networks, dial-up connections, wireless connections, and the Internet.
    There are also detailed blogs and similar thread for your reference.
    Distributed Databases in SQL Server 2005
    http://www.c-sharpcorner.com/UploadFile/john_charles/DistributeddatabasesinSQLServer11122007092249AM/DistributeddatabasesinSQLServer.aspx
    SQL SERVER – Shard No More – An Innovative Look at Distributed Peer-to-peer SQL Database
    http://blog.sqlauthority.com/2012/11/27/sql-server-shard-no-more-an-innovative-look-at-distributed-peer-to-peer-sql-database/
    How to implement distributed database in SQL Server 2008 R2?
    http://stackoverflow.com/questions/7926773/how-to-implement-distributed-database-in-sql-server-2008-r2
    Thanks,
    Lydia Zhang

  • Distributed Database  with IPV6

    Distributed database was not that familiar few years before...will IPv6 enhance the distributed database systems ? DDBMS has wide range of best features & notable drawbacks to..however today's business need of distributed database. contribution of DDBMS in Cloud computing.

    user4422434 wrote:
    Distributed database was not that familiar few years before...will IPv6 enhance the distributed database systems ? No. Distributed databases have been common in the last century too.. running across IPv4 and Novel IPX networks.
    Do not confuse the communication transport layer with the ability of the database to support distributed integration. Even NetBEUI can be used (assuming that protocol routing is not needed). Distributed database is not about protocol dependency.

  • RE: Distributed database [Ref:C776312]

    By "distributed database", do you mean that the database lives on several
    servers, or that the database lives on one server which is distributed from the
    application ?
    Steve Elvin
    Systems Developer
    Frontline Ltd.
    UK
    -----Original Message-----
    From: INTERNET [email protected]
    Sent: Friday, October 23, 1998 12:13 AM
    To: Steve Elvin; X400
    p=NET;a=CWMAIL;c=GB;DDA:RFC-822=forte-users(a)sageit.com;
    Subject: Distributed database [Ref:C776312]
    Hi Everyone,
    We are looking at different options to connect the forte application to
    distributed database.
    Any help greatly appreciated
    Thanks & Regards
    Raju
    (Pothuraju Katta)
    [email protected]
    Phone: 847-969-3000
    Fax: 847-995-8287
    To unsubscribe, email '[email protected]' with
    'unsubscribe forte-users' as the body of the message.
    Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>
    To unsubscribe, email '[email protected]' with
    'unsubscribe forte-users' as the body of the message.
    Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>

    By "distributed database", do you mean that the database lives on several
    servers, or that the database lives on one server which is distributed from the
    application ?
    Steve Elvin
    Systems Developer
    Frontline Ltd.
    UK
    -----Original Message-----
    From: INTERNET [email protected]
    Sent: Friday, October 23, 1998 12:13 AM
    To: Steve Elvin; X400
    p=NET;a=CWMAIL;c=GB;DDA:RFC-822=forte-users(a)sageit.com;
    Subject: Distributed database [Ref:C776312]
    Hi Everyone,
    We are looking at different options to connect the forte application to
    distributed database.
    Any help greatly appreciated
    Thanks & Regards
    Raju
    (Pothuraju Katta)
    [email protected]
    Phone: 847-969-3000
    Fax: 847-995-8287
    To unsubscribe, email '[email protected]' with
    'unsubscribe forte-users' as the body of the message.
    Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>
    To unsubscribe, email '[email protected]' with
    'unsubscribe forte-users' as the body of the message.
    Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>

  • Installtion of standalone gateway on db server

    Dear Gurus,
    I am going to install standalone gateway installation on my DB host.
    It is because my RFC connection in CI  [SAPXPG_DBDEST_DBHOSTNAME]  is failing.
    the failure of this RFC causing failure of server DBA jobs .
    System is at 640 version,
    Could you please let me know do we need any post installation steps after i install gateway
    standalone engine?
    Thanks and Regards
    Purna

    Hi Purna,
    There are no post installation steps as such.
    If your standalone gateway is running on the DB server , then just enter the gateway parameters in SAPXPG_DBDEST_DBHOSTNAME  and do a test run.
    Is the test works fine, then your DB activities should also run.
    Cheeers......,
    Raghu

  • Distributed database environment

    In my one Jheadstart project, it will meet distributed database environment, that is some one project's application data be located in different oracle database .
    How to treat this situation, about in one project to handle distributed database environment ?
    Is the jheadstart support multi database connection ?
    or need through database link capacity to fulfill !

    Ting Rung,
    There is at least one thing that you might run into, and that is the issue of transaction management. An application module represents a 'data model' for a tak that is accomplished within one transaction. You can nest application modules, but even then will the top-level application module provide the transaction context.
    This means that all data that necessarily needs to be persisted in one transaction, needs to be represented by the same (hierarcy of) application module(s) and therefore must come from the same data source (database). Said in other words: when the customers are in one database and the orders in another, you cannot persist them in one and the same transaction.
    There are more issues related to distributed applications. I have no experience with that, so I cannot comment on that. I do know that many distributed enterprise applications make use of EJB technology. BC4J supports entity beans (to be compared with entity and view objects). It also knows EJB application modules that behave like session beans. JHeadstart does not support using EJBs, however.
    For further information about the support for EJB technology, I would like to refer you to the online help of JDeveloper.
    Jan Kettenis
    JHeadstart Team

  • To Design Distributed Database?

    What Architecture should I follow to Design Distributed Database?
    By using Forms at frount_end How do I design the Schema of client and server Database
    .

    I think you can use Java Trasaction API that is independent of the Resources and will give you more flexibility to handle trasactions
    This link may be helpful
    http://www.onjava.com/pub/a/onjava/2001/05/23/j2ee.html

  • Difference between Instance Crash and Database Crash in Standalone and RAC?

    I am new to Oracle Environment. I would appreiciate if i get clarified on the "_+Difference between Instance Crash and Database Crash in Standalone and
    RAC_".+
    Oracle Version: 11.1.0.7.0
    O.S Version: HP-UX B.11.31 U

    Sivaprasad S wrote:
    I am new to Oracle Environment. I would appreiciate if i get clarified on the "_+Difference between Instance Crash and Database Crash in Standalone and
    RAC_".+That depends on your definitions of database crash versus instance crash.
    Literally, database crash means that the database itself is damaged in some way. A disk is no more. Data files are corrupted. Etc. The database itself thus causes the crash - and a database crash will also cause all database instances (RAC or single) for that database to crash too.
    An instance crash will therefore mean that the crash occurs in the instance due to an Oracle bug or similar. In other words a s/w error and not a database error. The database is still "fine", but the instance not. Instance crashes. However, any other instance on that same (RAC) database will still be fine as the database itself is unaffected by that s/w error in the crashed instance.
    If you mean something different, please enlighten us. Not all crashes are equal. {noformat};-){noformat}

Maybe you are looking for