SAP BPC Partitioning on a Windows 64 bit Server

Hello, we are considering SQL Server 2005 partitioning the SAP BPC (V5 SP3) time dimension by month on a Windows 64 bit Server since we curently have more than 70 million records in the application FACT table.  Has any body got any experience of partitioning with Windows 64 bit servers and if so can you provide ay recommendations and did you come across any issues that we should be aware of?

Hi Wayne,
It is no difference between 64 bits and 32 bits regarding the partioning of SQL 2005.
I think you would like to partition the cubes not the table.
Partioning of table doesn't help for performances but partionning of cube for OLAP it is provide at least 40% improvements for retrieve data (mdx queries).
So if you know to do the partitioning for 32 bits then you have to follow the same steps for 64 bits.
If you need information about how to do partitions in general then you can find into wiki information about how you can do partitions for BPC 5.X.
Regards
Sorin Radulescu

Similar Messages

  • I've installed SAP in my PC with windows 2000 server family....... .......

    I've installed SAP in my PC with windows 2000 server family... I want to upgrade my OS to XP. Can it be possible without unmounting SAP??? Please help me.

    Hi Pratap,
    SAP doesn't work with XP, it works only server Operating System.
    But u can instal XP in the system without currupting the SAP.
    Make sure that your HDD having atleast 3 partitions.
    The first two partintions (Ex.C:/& D:/) may have 2000 Server and SAP respectively.
    In the 3rd Partition (Ex.E:/) u can instal XP. but better to not touch 1st two Partitions
    To Instal XP follow these steps.
    Insert XP OS CD
    Restat the System
    follow installation procedure according CD
    Finally select E:/ to install XP.
    Pls let me know your feedback
    Regards
    Raveendra

  • Running SAP Business One on a 64-bit server

    One of our clients wants to upgrade their server to a 64-bit server running Windows Server 2008.
    What are the implications of this and do we also need to then use Microsoft SQL Server 2008?
    I went to this web link: https://websmp103.sap-ag.de/smb/sbo/platforms and found some info, but the questions I still have is the following:
    1. If we upgrade to SQL 2008, do we have to buy licenses or can we also just get an installation from SAP with our software (if we've gone live over 2 years ago already on SQL 2000, then upgraded to SQL 2005).
    2. Can we still stay on SQL 2005 or is it better to use SQL 2008 and what is the implications?
    I found the following on the link posted above:
    Mar 11: SAP Business One 2007 now supports Microsoft® SQL Server 2008.
    Microsoft SQL Server 2008 is now fully supported by SAP Business One 2007 A (as of patch 47) and SAP Business One 2007 B (as of patch 10), including SAP-developed add-ons.
    Jan 21: SAP Business One 2007 now supports Microsoft® Windows Server 2008.
    Microsoft Windows Server 2008 is now fully supported by SAP Business One 2007 A (as of patch 46) and SAP Business One 2007 B (as of patch 09), including SAP-developed add-ons. 64-bit and WTS support are still pending and will be announced when available.
    What exactly does the bold part mean?
    Any tips/hints on making this decision will be greatly appreciated!
    Thanks,
    Adele

    Hi Adele,
    "64-bit and WTS support are still pending and will be announced when available" means that Windows 2008 64bit has not been tested working with SAP Business One yet. Thus not supported (yet).
    Same applies to W indows T erminal S erver 32bit and 64bit.
    >
    Adele le Roux wrote:
    > 1. If we upgrade to SQL 2008, do we have to buy licenses or can we also just get an installation from SAP with our software (if we've gone live over 2 years ago already on SQL 2000, then upgraded to SQL 2005
    I am not sure if procedure as described in note [928839|https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMSZ3PTU4ODAwMDAr)/bc/bsp/spn/smb_searchnotes/display.htm?note_langu=E&note_numm=928839] will apply. In order to get excact clarification I have asked the owner of the note to update it reagarding MSSQL 2008 licenses.
    >
    Adele le Roux wrote:
    > 2. Can we still stay on SQL 2005 or is it better to use SQL 2008 and what is the implications?.
    Yes, you can still stay on MSSQL 2005 and upgrade later to MSSQL 2008. The other way around will not work. MSSQL 2008 is currently supported only as of SAP Business One 2007 A PL47 or SAP Business One 2007 B PL10. Refer to [http://service.sap.com/smb/sbo/platforms|http://service.sap.com/smb/sbo/platforms].
    Regards
    Mario

  • Bank Statement management in SAP B1 on a VMWare Windows 2008 server

    Hi everybody,
    One of our customer is using a VMWare Windows 2008 server with SAP B1.
    Actual version of Business One is SBO 2007A PL 00 PL 15 (SQL Server 2005).
    Since the installation of this server using VMWare, we encouter problems using the SAP B1 Integration Platform for the process of the bank statements.
    Everything including bank statements transfer was working very fine on a "real" server before new implementation.
    When trying to open the Integration Platform Control Center on the server, we now receive the following message regarding JAVA.
    "JAVA Virtual Machine Launcher : could not find the main class : program will exit."
    JAVA is well installed on the VMWare server.
    We have searched for a solution on the Web and it seems that JAVA and VMWare are not compatible. Does anybody have any information about that ?
    Does anybody already have this problem with Integration Platfom on VMWare server ?
    Is there a solution to our problem ?
    Thanks for all your contributions.
    Best regards.
    Michel

    Hi Michel,
    First of all, your PL is too low.  AFAIK, the first supported PL for 2007A SP00 is PL30.  You may upgrade your PL first to see if that is a bug or not.
    Thanks,
    Gordon

  • Install SAP GUI 7.20 on Windows terminal server

    Hi,
    I would like to install SAP GUI 7.20 on a Windows Terminal Server and configure it so that all users on the terminal server share a common configuration. As the installation is now all users have to define the systems in GUI the first time they start it, but I would like to do this globally. Is this possible?
    Best regards,
    Thor-Egil

    > estimated 20 or more users who will be using the WTS to do their specific transaction. How much ram do we need to put in the WTS to handle 20 or more users?
    This depends on what the users will do on that system. I suggest you contact the hardware vendor for a sizing of the machine.
    > and follow up question, do you recommend using terminal servers?
    It's an easy way to centralize the administration, you have got only one SAPGui installation.
    Markus

  • SAP GUI Memory issues on Windows Terminal Server 2003!!

    Hi All
    We are currently experiencing serious issues with our terminal servers and SAP GUI. It appears that SAP GUI is consuming a large amount of memory inorder to run, which in term is causing our terminal servers to page more.
    I am not sure where to start with this issue so any help would be great!
    Thanks
    Phil
    Loads of points if someone helps me solve this!!!

    Citrix won´t help much, it´s "just" a different protocol between the client and the server, Citrix itself will use even more memory.
    Why are you sure, that the reason for this is the SAPGUI and not any other Office program?
    Let´s calculate:
    I´m writing this message on a TS too. My Outlook (2003) consumes ~ 32 MB memory (incl. virtual), I have 4 SAPGUI windows open which consume 64 MB and some telnet sessions (no Word, Excel etc.)
    Let say roughly 128 MB all in all.
    If you have 2000 users with 20 servers, means, 100 users on one server, that would be 12,8 GB memory - not caclulated other services running on that box (printserver etc.) including the operating system itself.
    If your users have Internet Explorer (or other browsers) open too, you will need to add that amount too. 128 MB per user is the minimum.
    If users use BEx (or other .NET based BI developer tools), that amount will doubled (at least).
    SAP recommends a PC with at least 256 MB memory to run a SAPGUI with acceptable performance, do you have that much per users? How big are your single servers?
    Markus

  • Error in installation of SAP IDES 4.7 in windows 2000 server

    hi i m getting error in sap ides 4.7 installation i m giving here error log and my environment variables list..can anyone help me ...
    Following is list of Environment varialbes...
    VARIABLE     VALUE
    DBMS_TYPE     ORA
    DBS_ORA_SCHEMA  SAPO02
    dbs_ora_tnsname o02
    JAVA           D:\JDK1.3.1_03\BIN
    NLS_LANG     AMERICAN_AMERICA.WE8DEC
    ora          D:\oracle\o02\917\bin\sqlplus.exe
    ORACLE_HOME     D:\ORACLE\O02\917
    ORACLE_SID     O02
    PATH          D:\usr\sap\o02\SYS\exe\run
    SAPDATA_HOME     D:\oracle\o02
    SAPEXE          D:\usr\sap\o02\SYS\exe\run
    SAPLOCALHOST     nainesh
    TEMP          D:\WINNT\TEMP
    TMP          D:\WINNT\TEMP
    Getting error in this step...
    oracle pre-load action.
    Following  is log file....at last error is indicated....:---
    INFO 2008-02-17 13:03:01
    Processing of host operation t_HostInfo_SHARED succeeded.
    INFO 2008-02-17 13:03:14
    The 'saploc' share exists at directory 'D:\usr\sap'. Choosing drive D: as SAP System drive.
    INFO 2008-02-17 13:03:27
    Copying file E:/NT/COMMON/OraVolatileDatabaseParameters.xml to: OraVolatileDatabaseParameters.xml.
    INFO 2008-02-17 13:03:27
    Creating file D:\SAPinst ORACLE KERNEL\OraVolatileDatabaseParameters.xml.
    INFO 2008-02-17 13:04:28
    Copying file C:/sap-source/exp1/DB/ORA/DBSIZE.XML to: DBSIZE.XML.
    INFO 2008-02-17 13:04:28
    Creating file D:\SAPinst ORACLE KERNEL\DBSIZE.XML.
    INFO 2008-02-17 13:04:28
    Copying file system node C:\sap-source\exp1/DB/ORA/DBSIZE.XML with type NODE to DBSIZE.XML succeeded.
    INFO 2008-02-17 13:04:28
    Processing of all file system node operations of table tORA_filecopy succeeded.
    INFO 2008-02-17 13:04:29
    Copying file C:/sap-source/exp1/DB/DDLORA.TPL to: DDLORA.TPL.
    INFO 2008-02-17 13:04:29
    Creating file D:\SAPinst ORACLE KERNEL\DDLORA.TPL.
    INFO 2008-02-17 13:04:29
    Copying file system node C:\sap-source\exp1/DB/DDLORA.TPL with type NODE to DDLORA.TPL succeeded.
    INFO 2008-02-17 13:04:29
    Processing of all file system node operations of table tORA_filecopy succeeded.
    INFO 2008-02-17 13:04:29
    Moving file D:/SAPinst ORACLE KERNEL/DDLORA.TPL to: orig_ddl_ora_tmp.tpl.
    INFO 2008-02-17 13:04:29
    Moving file D:/SAPinst ORACLE KERNEL/changed_ddl_ora_tmp.tpl to: DDLORA.TPL.
    INFO 2008-02-17 13:04:29
    Removing file D:/SAPinst ORACLE KERNEL/orig_ddl_ora_tmp.tpl.
    INFO 2008-02-17 13:05:14
    Package table created
    PHASE 2008-02-17 13:05:49
    SAP R/3 Enterprise 4.70 for Oracle
    PHASE 2008-02-17 13:05:49
    SAP Web Application Server
    PHASE 2008-02-17 13:05:49
    Request common parameters of SAP System
    PHASE 2008-02-17 13:05:49
    Create operating system accounts
    INFO 2008-02-17 13:05:50
    Copying file D:/SAPinst ORACLE KERNEL/keydb.xml to: D:/SAPinst ORACLE KERNEL/keydb.1.xml.
    INFO 2008-02-17 13:05:50
    Creating file D:\SAPinst ORACLE KERNEL\keydb.1.xml.
    INFO 2008-02-17 13:05:51
    Copying file D:/SAPinst ORACLE KERNEL/OraVolatileDatabaseParameters.xml to: D:/SAPinst ORACLE KERNEL/OraVolatileDatabaseParameters.1.xml.
    INFO 2008-02-17 13:05:51
    Creating file D:\SAPinst ORACLE KERNEL\OraVolatileDatabaseParameters.1.xml.
    INFO 2008-02-17 13:05:51
    Copying file D:/SAPinst ORACLE KERNEL/DBSIZE.XML to: D:/SAPinst ORACLE KERNEL/DBSIZE.1.XML.
    INFO 2008-02-17 13:05:51
    Creating file D:\SAPinst ORACLE KERNEL\DBSIZE.1.XML.
    INFO 2008-02-17 13:05:51
    Changing account ACCOUNTID=S-1-5-21-1993962763-1454471165-725345543-1004 ACCOUNTNAME=nainesh\SAP_LocalAdmin ACCOUNTTYPE=GROUP DESCRIPTION=SAP Local Administration Group MEMBERSHIPSEPARATOR=, OPMODE=CREATE  succeeded.
    INFO 2008-02-17 13:05:51
    Changing account ACCOUNTID=S-1-5-21-1993962763-1454471165-725345543-1005 ACCOUNTNAME=nainesh\SAP_O02_LocalAdmin ACCOUNTTYPE=GROUP DESCRIPTION=SAP Local Administration Group MEMBERSHIPSEPARATOR=, OPMODE=CREATE  succeeded.
    INFO 2008-02-17 13:05:51
    Changing account ACCOUNTID=S-1-5-21-1993962763-1454471165-725345543-1006 ACCOUNTNAME=nainesh\SAP_O02_GlobalAdmin ACCOUNTTYPE=GROUP DESCRIPTION=SAP Global Administration Group MEMBERSHIPSEPARATOR=, OPMODE=CREATE  succeeded.
    INFO 2008-02-17 13:05:51
    Changing account ACCOUNTID=S-1-5-21-1993962763-1454471165-725345543-1007 ACCOUNTNAME=ORA_O02_DBA ACCOUNTTYPE=GROUP CONDITION=YES DESCRIPTION=Database Operator Group MEMBERSHIPSEPARATOR=, OPMODE=CREATE  succeeded.
    INFO 2008-02-17 13:07:20
    File system node D:\oracle\O02/sapdata2\roll_1 exists already. Nothing to do.
    INFO 2008-02-17 13:07:20
    File system node D:\oracle\O02/sapdata3\temp_1 exists already. Nothing to do.
    INFO 2008-02-17 13:07:20
    File system node D:\oracle\O02/sapdata1\system_1 exists already. Nothing to do.
    INFO 2008-02-17 13:07:20
    Processing of all file system node operations of table tORA_SapdataNodes succeeded.
    INFO 2008-02-17 13:07:20
    Processing of all file system node operations of table tORA_DatabaseServerNodes succeeded.
    INFO 2008-02-17 13:07:21
    Processing of all file system node operations of table tORA_SapdataNodes succeeded.
    INFO 2008-02-17 13:07:22
    Removing file D:/ORACLE/O02/917/database/initO02.ora.bak.
    INFO 2008-02-17 13:07:22
    Moving file D:/ORACLE/O02/917/database/initO02.ora to: D:\ORACLE\O02\917/database/initO02.ora.bak.
    INFO 2008-02-17 13:07:22
    Creating file D:\ORACLE\O02\917\database\initO02.ora.
    INFO 2008-02-17 13:07:24
    Removing file D:/ORACLE/O02/917/database/initO02.sap.bak.
    INFO 2008-02-17 13:07:24
    Moving file D:/ORACLE/O02/917/database/initO02.sap to: D:\ORACLE\O02\917/database/initO02.sap.bak.
    INFO 2008-02-17 13:07:24
    Creating file D:\ORACLE\O02\917\database\initO02.sap.
    INFO 2008-02-17 13:07:26
    Removing file D:/ORACLE/O02/917/database/initO02.dba.bak.
    INFO 2008-02-17 13:07:26
    Moving file D:/ORACLE/O02/917/database/initO02.dba to: D:\ORACLE\O02\917/database/initO02.dba.bak.
    INFO 2008-02-17 13:07:26
    Copying file E:/NT/COMMON/INSTALL/INITSID.DBA to: D:\ORACLE\O02\917/database/initO02.dba.
    INFO 2008-02-17 13:07:26
    Creating file D:\ORACLE\O02\917\database\initO02.dba.
    INFO 2008-02-17 13:07:27
    Changed working directory to D:\SAPinst ORACLE KERNEL.
    INFO 2008-02-17 13:07:36
    Removing file D:/oracle/O02/sapdata1/o02_1/o02.data1.
    INFO 2008-02-17 13:07:36
    Removing file D:/oracle/O02/sapdata2/o02_2/o02.data2.
    INFO 2008-02-17 13:07:36
    Removing file D:/oracle/O02/sapdata2/o02_3/o02.data3.
    INFO 2008-02-17 13:07:36
    Removing file D:/oracle/O02/sapdata2/o02_4/o02.data4.
    INFO 2008-02-17 13:07:36
    Removing file D:/oracle/O02/sapdata3/o02_5/o02.data5.
    INFO 2008-02-17 13:07:36
    Removing file D:/oracle/O02/sapdata3/o02_6/o02.data6.
    INFO 2008-02-17 13:07:36
    Removing file D:/oracle/O02/sapdata4/o02_7/o02.data7.
    INFO 2008-02-17 13:07:36
    Removing file D:/oracle/O02/sapdata4/o02_8/o02.data8.
    INFO 2008-02-17 13:07:36
    Removing file D:/oracle/O02/sapdata1/o02620_1/o02620.data1.
    INFO 2008-02-17 13:07:36
    Removing file D:/oracle/O02/sapdata1/o02620_2/o02620.data2.
    INFO 2008-02-17 13:07:36
    Removing file D:/oracle/O02/sapdata1/o02620_3/o02620.data3.
    INFO 2008-02-17 13:07:36
    Removing file D:/oracle/O02/sapdata2/o02620_4/o02620.data4.
    INFO 2008-02-17 13:07:36
    Removing file D:/oracle/O02/sapdata2/o02620_5/o02620.data5.
    INFO 2008-02-17 13:07:36
    Removing file D:/oracle/O02/sapdata3/o02620_6/o02620.data6.
    INFO 2008-02-17 13:07:36
    Removing file D:/oracle/O02/sapdata3/o02620_7/o02620.data7.
    INFO 2008-02-17 13:07:36
    Removing file D:/oracle/O02/sapdata4/o02620_8/o02620.data8.
    INFO 2008-02-17 13:07:36
    Removing file D:/oracle/O02/sapdata4/o02620_9/o02620.data9.
    INFO 2008-02-17 13:07:36
    Removing file D:/oracle/O02/sapdata4/o02620_10/o02620.data10.
    INFO 2008-02-17 13:07:20
    File system node D:\oracle\O02/sapdata2\roll_1 exists already. Nothing to do.
    INFO 2008-02-17 13:07:20
    File system node D:\oracle\O02/sapdata3\temp_1 exists already. Nothing to do.
    INFO 2008-02-17 13:07:20
    File system node D:\oracle\O02/sapdata1\system_1 exists already. Nothing to do.
    INFO 2008-02-17 13:07:20
    Processing of all file system node operations of table tORA_SapdataNodes succeeded.
    INFO 2008-02-17 13:07:20
    Processing of all file system node operations of table tORA_DatabaseServerNodes succeeded.
    INFO 2008-02-17 13:07:21
    Processing of all file system node operations of table tORA_SapdataNodes succeeded.
    INFO 2008-02-17 13:07:22
    Removing file D:/ORACLE/O02/917/database/initO02.ora.bak.
    INFO 2008-02-17 13:07:22
    Moving file D:/ORACLE/O02/917/database/initO02.ora to: D:\ORACLE\O02\917/database/initO02.ora.bak.
    INFO 2008-02-17 13:07:22
    Creating file D:\ORACLE\O02\917\database\initO02.ora.
    INFO 2008-02-17 13:07:24
    Removing file D:/ORACLE/O02/917/database/initO02.sap.bak.
    INFO 2008-02-17 13:07:24
    Moving file D:/ORACLE/O02/917/database/initO02.sap to: D:\ORACLE\O02\917/database/initO02.sap.bak.
    INFO 2008-02-17 13:07:24
    Creating file D:\ORACLE\O02\917\database\initO02.sap.
    INFO 2008-02-17 13:07:26
    Removing file D:/ORACLE/O02/917/database/initO02.dba.bak.
    INFO 2008-02-17 13:07:26
    Moving file D:/ORACLE/O02/917/database/initO02.dba to: D:\ORACLE\O02\917/database/initO02.dba.bak.
    INFO 2008-02-17 13:07:26
    Copying file E:/NT/COMMON/INSTALL/INITSID.DBA to: D:\ORACLE\O02\917/database/initO02.dba.
    INFO 2008-02-17 13:07:26
    Creating file D:\ORACLE\O02\917\database\initO02.dba.
    INFO 2008-02-17 13:07:27
    Changed working directory to D:\SAPinst ORACLE KERNEL.
    INFO 2008-02-17 13:07:36
    Removing file D:/oracle/O02/sapdata1/o02_1/o02.data1.
    INFO 2008-02-17 13:07:36
    Removing file D:/oracle/O02/sapdata2/o02_2/o02.data2.
    INFO 2008-02-17 13:07:36
    Removing file D:/oracle/O02/sapdata2/o02_3/o02.data3.
    INFO 2008-02-17 13:07:36
    Removing file D:/oracle/O02/sapdata2/o02_4/o02.data4.
    INFO 2008-02-17 13:07:36
    Removing file D:/oracle/O02/sapdata3/o02_5/o02.data5.
    INFO 2008-02-17 13:07:36
    Removing file D:/oracle/O02/sapdata3/o02_6/o02.data6.
    INFO 2008-02-17 13:07:36
    Removing file D:/oracle/O02/sapdata4/o02_7/o02.data7.
    INFO 2008-02-17 13:07:36
    Removing file D:/oracle/O02/sapdata4/o02_8/o02.data8.
    INFO 2008-02-17 13:07:36
    Removing file D:/oracle/O02/sapdata1/o02620_1/o02620.data1.
    INFO 2008-02-17 13:07:36
    Removing file D:/oracle/O02/sapdata1/o02620_2/o02620.data2.
    INFO 2008-02-17 13:07:36
    Removing file D:/oracle/O02/sapdata1/o02620_3/o02620.data3.
    INFO 2008-02-17 13:07:36
    Removing file D:/oracle/O02/sapdata2/o02620_4/o02620.data4.
    INFO 2008-02-17 13:07:36
    Removing file D:/oracle/O02/sapdata2/o02620_5/o02620.data5.
    INFO 2008-02-17 13:07:36
    Removing file D:/oracle/O02/sapdata3/o02620_6/o02620.data6.
    INFO 2008-02-17 13:07:36
    Removing file D:/oracle/O02/sapdata3/o02620_7/o02620.data7.
    INFO 2008-02-17 13:07:36
    Removing file D:/oracle/O02/sapdata4/o02620_8/o02620.data8.
    INFO 2008-02-17 13:07:36
    Removing file D:/oracle/O02/sapdata4/o02620_9/o02620.data9.
    INFO 2008-02-17 13:07:36
    Removing file D:/oracle/O02/sapdata4/o02620_10/o02620.data10.
    INFO 2008-02-17 13:07:36
    Removing file D:/oracle/O02/sapdata4/o02usr_1/o02usr.data1.
    INFO 2008-02-17 13:07:36
    Removing file D:/oracle/O02/sapdata2/roll_1/roll.data1.
    INFO 2008-02-17 13:07:36
    Removing file D:/oracle/O02/sapdata3/temp_1/temp.data1.
    INFO 2008-02-17 13:07:36
    Removing file D:/oracle/O02/sapdata1/system_1/system.data1.
    INFO 2008-02-17 13:07:36
    Removing file D:/oracle/O02/sapdata1/cntrl/cntrlO02.dbf.
    INFO 2008-02-17 13:07:36
    Removing file D:/oracle/O02/saparch/cntrl/cntrlO02.dbf.
    INFO 2008-02-17 13:07:36
    Removing file D:/oracle/O02/origlogA/cntrl/cntrlO02.dbf.
    INFO 2008-02-17 13:07:37
    Moving file D:/ORACLE/O02/917/database/initO02.ora to: orig_init_ora_tmp.txt.
    INFO 2008-02-17 13:07:37
    Moving file D:/SAPinst ORACLE KERNEL/changed_init_ora_tmp.txt to: D:\ORACLE\O02\917\database\initO02.ora.
    INFO 2008-02-17 13:07:37
    Removing file D:/SAPinst ORACLE KERNEL/orig_init_ora_tmp.txt.
    INFO 2008-02-17 13:07:38
    Creating file D:\SAPinst ORACLE KERNEL\oradim.log.
    INFO 2008-02-17 13:07:38
    See 'D:\ORACLE\O02\917/bin/oradim -new -sid O02 -STARTMODE auto' output in 'D:\SAPinst ORACLE KERNEL\oradim.log'.
    INFO 2008-02-17 13:07:38
    'D:\ORACLE\O02\917/bin/oradim -new -sid O02 -STARTMODE auto' returned with '20'.
    INFO 2008-02-17 13:07:39
    Changed working directory to D:\SAPinst ORACLE KERNEL.
    INFO 2008-02-17 13:07:40
    Changed working directory to D:\SAPinst ORACLE KERNEL.
    INFO 2008-02-17 13:07:49
    Changed working directory to D:\SAPinst ORACLE KERNEL.
    INFO 2008-02-17 13:08:35
    Changed working directory to D:\SAPinst ORACLE KERNEL.
    INFO 2008-02-17 13:08:39
    Changed working directory to D:\SAPinst ORACLE KERNEL.
    INFO 2008-02-17 13:09:44
    Changed working directory to D:\SAPinst ORACLE KERNEL.
    INFO 2008-02-17 13:09:49
    Changed working directory to D:\SAPinst ORACLE KERNEL.
    INFO 2008-02-17 13:14:33
    Changed working directory to D:\SAPinst ORACLE KERNEL.
    INFO 2008-02-17 13:14:38
    Changed working directory to D:\SAPinst ORACLE KERNEL.
    INFO 2008-02-17 13:14:40
    Changed working directory to D:\SAPinst ORACLE KERNEL.
    INFO 2008-02-17 13:14:41
    Changed working directory to D:\SAPinst ORACLE KERNEL.
    INFO 2008-02-17 13:14:42
    Moving file D:/ORACLE/O02/917/database/initO02.ora to: orig_init_ora_tmp.txt.
    INFO 2008-02-17 13:14:42
    Moving file D:/SAPinst ORACLE KERNEL/changed_init_ora_tmp.txt to: D:\ORACLE\O02\917\database\initO02.ora.
    INFO 2008-02-17 13:14:42
    Removing file D:/SAPinst ORACLE KERNEL/orig_init_ora_tmp.txt.
    INFO 2008-02-17 13:14:43
    Changed working directory to D:\SAPinst ORACLE KERNEL.
    INFO 2008-02-17 13:14:43
    Changed working directory to D:\SAPinst ORACLE KERNEL.
    INFO 2008-02-17 13:15:58
    Changed working directory to D:\SAPinst ORACLE KERNEL.
    INFO 2008-02-17 13:15:59
    Changed working directory to D:\SAPinst ORACLE KERNEL.
    INFO 2008-02-17 13:17:11
    Changed working directory to D:\SAPinst ORACLE KERNEL.
    INFO 2008-02-17 13:17:12
    Changed working directory to D:\SAPinst ORACLE KERNEL.
    INFO 2008-02-17 13:18:24
    Changed working directory to D:\SAPinst ORACLE KERNEL.
    INFO 2008-02-17 13:18:25
    Changed working directory to D:\SAPinst ORACLE KERNEL.
    INFO 2008-02-17 13:19:03
    Changed working directory to D:\SAPinst ORACLE KERNEL.
    INFO 2008-02-17 13:19:04
    Changed working directory to D:\SAPinst ORACLE KERNEL.
    INFO 2008-02-17 13:20:15
    Changed working directory to D:\SAPinst ORACLE KERNEL.
    INFO 2008-02-17 13:20:16
    Changed working directory to D:\SAPinst ORACLE KERNEL.
    INFO 2008-02-17 13:21:29
    Changed working directory to D:\SAPinst ORACLE KERNEL.
    INFO 2008-02-17 13:21:30
    Changed working directory to D:\SAPinst ORACLE KERNEL.
    INFO 2008-02-17 13:22:43
    Changed working directory to D:\SAPinst ORACLE KERNEL.
    INFO 2008-02-17 13:22:44
    Changed working directory to D:\SAPinst ORACLE KERNEL.
    INFO 2008-02-17 13:23:58
    Changed working directory to D:\SAPinst ORACLE KERNEL.
    INFO 2008-02-17 13:23:58
    Changed working directory to D:\SAPinst ORACLE KERNEL.
    INFO 2008-02-17 13:25:11
    Changed working directory to D:\SAPinst ORACLE KERNEL.
    INFO 2008-02-17 13:25:12
    Changed working directory to D:\SAPinst ORACLE KERNEL.
    INFO 2008-02-17 13:26:32
    Changed working directory to D:\SAPinst ORACLE KERNEL.
    INFO 2008-02-17 13:26:35
    Changed working directory to D:\SAPinst ORACLE KERNEL.
    INFO 2008-02-17 13:27:17
    Changed working directory to D:\SAPinst ORACLE KERNEL.
    INFO 2008-02-17 13:27:20
    Changed working directory to D:\SAPinst ORACLE KERNEL.
    INFO 2008-02-17 13:28:32
    Changed working directory to D:\SAPinst ORACLE KERNEL.
    INFO 2008-02-17 13:28:35
    Changed working directory to D:\SAPinst ORACLE KERNEL.
    INFO 2008-02-17 13:29:46
    Changed working directory to D:\SAPinst ORACLE KERNEL.
    INFO 2008-02-17 13:29:49
    Changed working directory to D:\SAPinst ORACLE KERNEL.
    INFO 2008-02-17 13:31:02
    Changed working directory to D:\SAPinst ORACLE KERNEL.
    INFO 2008-02-17 13:31:05
    Changed working directory to D:\SAPinst ORACLE KERNEL.
    INFO 2008-02-17 13:32:16
    Changed working directory to D:\SAPinst ORACLE KERNEL.
    INFO 2008-02-17 13:32:19
    Changed working directory to D:\SAPinst ORACLE KERNEL.
    INFO 2008-02-17 13:33:31
    Changed working directory to D:\SAPinst ORACLE KERNEL.
    INFO 2008-02-17 13:33:34
    Changed working directory to D:\SAPinst ORACLE KERNEL.
    INFO 2008-02-17 13:34:46
    Changed working directory to D:\SAPinst ORACLE KERNEL.
    INFO 2008-02-17 13:34:46
    Changed working directory to D:\SAPinst ORACLE KERNEL.
    INFO 2008-02-17 13:36:00
    Changed working directory to D:\SAPinst ORACLE KERNEL.
    INFO 2008-02-17 13:36:01
    Changed working directory to D:\SAPinst ORACLE KERNEL.
    INFO 2008-02-17 13:36:04
    Changed working directory to D:\SAPinst ORACLE KERNEL.
    INFO 2008-02-17 13:36:05
    Changed working directory to D:\SAPinst ORACLE KERNEL.
    INFO 2008-02-17 13:36:31
    Changed working directory to D:\SAPinst ORACLE KERNEL.
    INFO 2008-02-17 13:36:32
    Changed working directory to D:\SAPinst ORACLE KERNEL.
    INFO 2008-02-17 13:36:44
    Changed working directory to D:\SAPinst ORACLE KERNEL.
    INFO 2008-02-17 13:36:45
    Changed working directory to D:\SAPinst ORACLE KERNEL.
    INFO 2008-02-17 13:36:46
    Moving file D:/ORACLE/O02/917/database/initO02.ora to: orig_init_ora_tmp.txt.
    INFO 2008-02-17 13:36:46
    Moving file D:/SAPinst ORACLE KERNEL/changed_init_ora_tmp.txt to: D:\ORACLE\O02\917\database\initO02.ora.
    INFO 2008-02-17 13:36:46
    Removing file D:/SAPinst ORACLE KERNEL/orig_init_ora_tmp.txt.
    INFO 2008-02-17 13:36:47
    Creating file D:\SAPinst ORACLE KERNEL\lsnrctl.log.
    INFO 2008-02-17 13:36:50
    See 'D:\ORACLE\O02\917/bin/lsnrctl stat' output in 'D:\SAPinst ORACLE KERNEL\lsnrctl.log'.
    INFO 2008-02-17 13:36:50
    'D:\ORACLE\O02\917/bin/lsnrctl stat' returned with '3'.
    INFO 2008-02-17 13:36:50
    Creating file D:\SAPinst ORACLE KERNEL\lsnrctl.log.
    INFO 2008-02-17 13:36:51
    See 'D:\ORACLE\O02\917/bin/lsnrctl start' output in 'D:\SAPinst ORACLE KERNEL\lsnrctl.log'.
    INFO 2008-02-17 13:36:51
    'D:\ORACLE\O02\917/bin/lsnrctl start' returned with '0'.
    INFO 2008-02-17 13:36:56
    Copying file E:/NT/COMMON/INSTALL/ORADBUSR.SQL to: ./oradbusr.sql.
    INFO 2008-02-17 13:36:56
    Creating file D:\SAPinst ORACLE KERNEL\oradbusr.sql.
    INFO 2008-02-17 13:36:57
    Changed working directory to D:\SAPinst ORACLE KERNEL.
    INFO 2008-02-17 13:36:57
    Changed working directory to D:\SAPinst ORACLE KERNEL.
    ERROR 2008-02-17 13:37:02
    CJS-00084  SQL Statement or Script failed. Error Message: Executable D:\ORACLE\O02\917/bin/sqlplus.exe returns 3.
    ERROR 2008-02-17 13:37:02
    FJS-00012  Error when executing script.
    Thanks & Regards,
      Nainesh.

    Thank you very much
    HI dear,
    I found tht file i m pasting log of tht file here tell me whr is problem.
    ================================================================================
    2008-06-29, 03:46:17 SAPINST ORACLE start logging for
    connect  / as sysdba ;
    SHUTDOWN ABORT;
    exit;
    Output of SQL executing program:
    SQL*Plus: Release 9.2.0.2.0 - Production on Sun Jun 29 03:46:17 2008
    Copyright (c) 1982, 2002, Oracle Corporation.  All rights reserved.
    ERROR:
    ORA-12560: TNS:protocol adapter error
    ORA-12560: TNS:protocol adapter error
    SAPINST: End of output of SQL executing program E:\oracle\ora92/bin/sqlplus.exe.
    SAPINST found errors.
    SAPINST The current process environment may be found in sapinst_ora_environment.log.
    2008-06-29, 03:46:18 SAPINST ORACLE stop logging
    ================================================================================
    2008-06-29, 03:46:26 SAPINST ORACLE start logging for
    connect  / as sysdba ;
    SHUTDOWN ABORT;
    exit;
    Output of SQL executing program:
    SQL*Plus: Release 9.2.0.2.0 - Production on Sun Jun 29 03:46:26 2008
    Copyright (c) 1982, 2002, Oracle Corporation.  All rights reserved.
    Connected.
    ORACLE instance shut down.
    Disconnected from Oracle9i Enterprise Edition Release 9.2.0.2.1 - Production
    With the Partitioning, OLAP and Oracle Data Mining options
    JServer Release 9.2.0.2.0 - Production
    SAPINST: End of output of SQL executing program E:\oracle\ora92/bin/sqlplus.exe.
    2008-06-29, 03:46:26 SAPINST ORACLE stop logging
    ================================================================================
    2008-06-29, 03:46:27 SAPINST ORACLE start logging for
    connect  / as sysdba ;
    STARTUP NOMOUNT;
    exit;
    Output of SQL executing program:
    SQL*Plus: Release 9.2.0.2.0 - Production on Sun Jun 29 03:46:27 2008
    Copyright (c) 1982, 2002, Oracle Corporation.  All rights reserved.
    Connected to an idle instance.
    ORACLE instance started.
    Total System Global Area  309606996 bytes
    Fixed Size               453204 bytes
    Variable Size            150994944 bytes
    Database Buffers       156966912 bytes
    Redo Buffers              1191936 bytes
    Disconnected from Oracle9i Enterprise Edition Release 9.2.0.2.1 - Production
    With the Partitioning, OLAP and Oracle Data Mining options
    JServer Release 9.2.0.2.0 - Production
    SAPINST: End of output of SQL executing program E:\oracle\ora92/bin/sqlplus.exe.
    2008-06-29, 03:46:30 SAPINST ORACLE stop logging
    ================================================================================
    2008-06-29, 03:46:30 SAPINST ORACLE start logging for
    connect  / as sysdba ;
    CREATE DATABASE D11 CONTROLFILE REUSE  MAXLOGFILES 255 MAXLOGMEMBERS 3 MAXLOGHISTORY 1000 MAXDATAFILES 254 MAXINSTANCES 50 NOARCHIVELOG  CHARACTER SET WE8DEC NATIONAL CHARACTER SET UTF8 DATAFILE 'E:\oracle\D11/sapdata1\system_1\system.data1' SIZE 350M REUSE AUTOEXTEND OFF
      LOGFILE  GROUP 1 ('E:\oracle\D11\origlogA\log_g11m1.dbf', 'E:\oracle\D11\mirrlogA\log_g11m2.dbf') SIZE 50M REUSE,
    GROUP 2 ('E:\oracle\D11\origlogB\log_g12m1.dbf', 'E:\oracle\D11\mirrlogB\log_g12m2.dbf') SIZE 50M REUSE,
    GROUP 3 ('E:\oracle\D11\origlogA\log_g13m1.dbf', 'E:\oracle\D11\mirrlogA\log_g13m2.dbf') SIZE 50M REUSE,
    GROUP 4 ('E:\oracle\D11\origlogB\log_g14m1.dbf', 'E:\oracle\D11\mirrlogB\log_g14m2.dbf') SIZE 50M REUSE
    exit;
    Output of SQL executing program:
    SQL*Plus: Release 9.2.0.2.0 - Production on Sun Jun 29 03:46:30 2008
    Copyright (c) 1982, 2002, Oracle Corporation.  All rights reserved.
    Connected.
    Database created.
    Disconnected from Oracle9i Enterprise Edition Release 9.2.0.2.1 - Production
    With the Partitioning, OLAP and Oracle Data Mining options
    JServer Release 9.2.0.2.0 - Production
    SAPINST: End of output of SQL executing program E:\oracle\ora92/bin/sqlplus.exe.
    2008-06-29, 03:47:12 SAPINST ORACLE stop logging
    ================================================================================
    2008-06-29, 03:47:13 SAPINST ORACLE start logging for
    connect  / as sysdba ;
    CONNECT SYSTEM/MANAGER;
    exit;
    Output of SQL executing program:
    SQL*Plus: Release 9.2.0.2.0 - Production on Sun Jun 29 03:47:13 2008
    Copyright (c) 1982, 2002, Oracle Corporation.  All rights reserved.
    Connected.
    ERROR:
    ORA-06553: PLS-213: package STANDARD not accessible
    Error accessing package DBMS_APPLICATION_INFO
    Connected.
    Disconnected from Oracle9i Enterprise Edition Release 9.2.0.2.1 - Production
    With the Partitioning, OLAP and Oracle Data Mining options
    JServer Release 9.2.0.2.0 - Production
    SAPINST: End of output of SQL executing program E:\oracle\ora92/bin/sqlplus.exe.
    SAPINST found errors.
    SAPINST The current process environment may be found in sapinst_ora_environment.log.
    2008-06-29, 03:47:14 SAPINST ORACLE stop logging
    ==============================================================
    2008-06-29, 03:47:14 SAPINST ORACLE start logging for
    connect  / as sysdba ;
    @@E:\oracle\ora92/rdbms/admin/catalog.sql
    exit;
    Output of SQL executing program:
    SQL*Plus: Release 9.2.0.2.0 - Production on Sun Jun 29 03:47:14 2008
    Copyright (c) 1982, 2002, Oracle Corporation.  All rights reserved.
    Connected.
    Package created.
    Package body created.
    Grant succeeded.
    Package created.
    Synonym created.
    Grant succeeded.
    Table created.
    View created.
    Synonym created.
    Grant succeeded.
    View created.
    Synonym created.
    Grant succeeded.
    View created.
    Synonym created.
    Grant succeeded.
    View created.
    Synonym created.
    Grant succeeded.
    Package created.
    Package body created.
    No errors.
    Synonym created.
    Package created.
    Package body created.
    No errors.
    0 rows deleted.
    1 row created.
    Commit complete.
    PL/SQL procedure successfully completed.
    View created.
    Synonym created.
    Grant succeeded.
    View created.
    Synonym created.
    Grant succeeded.
    View created.
    Synonym created.
    Grant succeeded.
    View created.
    Synonym created.
    Grant succeeded.
    View created.
    Synonym created.
    Grant succeeded.
    View created.
    Synonym created.
    Grant succeeded.
    View created.
    Synonym created.
    Grant succeeded.
    View created.
    Synonym created.
    Grant succeeded.
    View created.
    Synonym created.
    Grant succeeded.
    View created.
    Synonym created.
    Grant succeeded.
    View created.
    Synonym created.
    Grant succeeded.
    View created.
    Synonym created.
    Grant succeeded.
    View created.
    Synonym created.
    Grant succeeded.
    View created.
    Synonym created.
    Grant succeeded.
    View created.
    Synonym created.
    Grant succeeded.
    View created.
    Synonym created.
    Grant succeeded.
    View created.
    Synonym created.
    Grant succeeded.
    View created.
    Synonym created.
    Grant succeeded.
    View created.
    Synonym created.
    Grant succeeded.
    View created.
    Synonym created.
    Grant succeeded.
    View created.
    Synonym created.
    Grant succeeded.
    View created.
    Synonym created.
    Grant succeeded.
    View created.
    Synonym created.
    Grant succeeded.
    View created.
    Synonym created.
    Grant succeeded.
    View created.
    Synonym created.
    Grant succeeded.
    View created.
    Synonym created.
    Grant succeeded.
    View created.
    Synonym created.
    Grant succeeded.
    View created.
    Synonym created.
    Grant succeeded.
    View created.
    Synonym created.
    Grant succeeded.
    View created.
    Synonym created.
    Grant succeeded.
    View created.
    Synonym created.
    Grant succeeded.
    View created.
    Synonym created.
    Grant succeeded.
    View created.
    Synonym created.
    Grant succeeded.
    View created.
    Synonym created.
    Grant succeeded.
    View created.
    Synonym created.
    Grant succeeded.
    View created.
    Synonym created.
    Grant succeeded.
    View created.
    Synonym created.
    Grant succeeded.
    View created.
    Synonym created.
    Grant succeeded.
    View created.
    Synonym created.
    Grant succeeded.
    View created.
    Synonym created.
    Grant succeeded.
    View created.
    Synonym created.
    Grant succeeded.
    View created.
    Synonym created.
    Grant succeeded.
    View created.
    Synonym created.
    Grant succeeded.
    View created.
    Synonym created.
    Grant succeeded.
    View created.
    Synonym created.
    Grant succeeded.
    View created.
    Synonym created.
    Grant succeeded.
    View created.
    Synonym created.
    Grant succeeded.
    View created.
    Synonym created.
    Grant succeeded.
    View created.
    Synonym created.
    Grant succeeded.
    View created.
    Synonym created.
    Grant succeeded.
    View created.
    Synonym created.
    Grant succeeded.
    View created.
    Synonym created.
    Grant succeeded.
    View created.
    Synonym created.
    Grant succeeded.
    View created.
    Synonym created.
    Grant succeeded.
    View created.
    Synonym created.
    Grant succeeded.
    View created.
    Synonym created.
    Grant succeeded.
    View created.
    Synonym created.
    Grant succeeded.
    View created.
    Synonym created.
    Grant succeeded.
    View created.
    Synonym created.
    Grant succeeded.
    View created.
    Synonym created.
    Grant succeeded.
    View created.
    Synonym created.
    Grant succeeded.
    View created.
    Synonym created.
    Grant succeeded.
    View created.
    Synonym created.
    Grant succeeded.
    View created.
    Synonym created.
    Grant succeeded.
    View created.
    Synonym created.
    Grant succeeded.
    View created.
    Synonym created.
    Grant succeeded.
    View created.
    Synonym created.
    Grant succeeded.
    View created.
    Synonym created.
    Grant succeeded.
    View created.
    Synonym created.
    Grant succeeded.
    View created.
    Synonym created.
    Grant succeeded.
    View created.
    Synonym created.
    Grant succeeded.
    View created.
    Synonym created.
    Grant succeeded.
    View created.
    Synonym created.
    Grant succeeded.
    View created.
    Synonym created.
    Grant succeeded.
    View created.
    Synonym created.
    Grant succeeded.
    View created.
    Synonym created.
    Grant succeeded.
    View created.
    Synonym created.
    Grant succeeded.
    View created.
    Synonym created.
    Grant succeeded.
    View created.
    Synonym created.
    Grant succeeded.
    View created.
    Synonym created.
    Grant succeeded.
    View created.
    Synonym created.
    Grant succeeded.
    View created.
    Synonym created.
    Grant succeeded.
    View created.
    Synonym created.
    Grant succeeded.
    View created.
    Synonym created.
    Grant succeeded.
    View created.
    Synonym created.
    Grant succeeded.
    View created.
    Synonym created.
    Grant succeeded.
    View created.
    Synonym created.
    Grant succeeded.
    View created.
    Synonym created.
    Grant succeeded.
    View created.
    Synonym created.
    Grant succeeded.
    View created.
    Synonym created.
    Grant succeeded.
    View created.
    Synonym created.
    Grant succeeded.
    View created.
    Synonym created.
    Grant succeeded.
    View created.
    Synonym created.
    Grant succeeded.
    View created.
    Synonym created.
    Grant succeeded.
    View created.
    Synonym created.
    Grant succeeded.
    View created.
    Synonym created.
    Grant succeeded.
    View created.
    Synonym created.
    Grant succeeded.
    View created.
    Synonym created.
    Grant succeeded.
    View created.
    Synonym created.
    Grant succeeded.
    View created.
    Synonym created.
    Grant succeeded.
    View created.
    Synonym created.
    Grant succeeded.
    View created.
    Synonym created.
    Grant succeeded.
    View created.
    Synonym created.
    Grant succeeded.
    View created.
    Synonym created.
    Grant succeeded.
    View created.
    Synonym created.
    Grant succeeded.
    View created.
    Synonym created.
    Grant succeeded.
    View created.
    Synonym created.
    Grant succeeded.
    View created.
    Synonym created.
    Grant succeeded.

  • SAP AFARIA 7.0 in windows 2012 server

    Hi,
    I triedto install Afaria in windows server 2012. Installation of afaria and api goes fine.But when I install the package server it gives the error install MS.Net Windows communication  Foundation.After installing all the required components and IIS it throes the same error.Please suggest whether its because  OS not compatible or some missing components

    Hi Vijay
    Before that check the PAM, http://service.sap.com/pam
    BR
    SS

  • Install 2 SAP BPC 7.0 MS SP4 in the same machine.

    Hello,
    I want to know if itu2019s possible to install 2 SAP BPC 7.0 MS SP4 in the same machine.
    I think that is impossible because the Osoft is unique and the COM+ is unique too. For the IIS and SQL I know that you can have more than one instance, but those two I know I can't.
    Please, can someone confirm this?.
    But if it's possible, how can I do this?
    Best regards.
    Pablo Mortera.

    Hi Pablo
    As per Nilanjan's post, I also don't understand why you want to do this,
    Do you want to install 2 different instances of SAP BPC on the same Windows server or possibly two seperate virtual servers on a physical host ?
    but none the less, in theory you can do it.
    You will need to create two different websites in IIS and when you do the installation make sure that you select the correct IIS web site, so that it doesnt attempt to recreate the virtual directory on the same IIS web site again during the second installation
    Kind Regards
    Daniel

  • SAP BPC 7 APPSet Restore SQL 2005

    Hi Everyone,
    I have SAP BPC 7 setup in a multi-server environment, and it's working well. I created a dev environment, installed SAP in the same fashion, and now when I try to restore an app set through server manager in dev, it keeps putting the SQL DB on C instead of where it should go on I:\ .
    The original app set was using this same drive configuration, and that backup/restore works fine -
    I've gotten this to work before, but I can't seem to get the restore to go somewhere else this time...
    Any thoughts appreciated -
    Edward

    Hi,
    More testing today so let's share
    There is 3 registry key in SQL Server 2005 :
    HKLM\SOFTWARE\Microsoft\Microsoft SQL Server\<Instance Name>\MSSQLServer\DefaultData
    HKLM\SOFTWARE\Microsoft\Microsoft SQL Server\<Instance Name>\MSSQLServer\DefaultLog
    HKLM\SOFTWARE\Microsoft\Microsoft SQL Server\<Instance Name>\Setup\SQLDataRoot
    Key #1 and key #2 are the one you configure in SQL server Manager and they correspond to the *.MDF directory and *.LDF directory.
    Key #3 is the one you configure during SQL Server installation.
    SAP Server manager will use key #3 when you restore an appset and also during the installation process of the ApShell.
    Key #1 and Key #2 are used by BPC setup to create the AppServer database.
    So to conclude : Even if you change Key #3 value in order to change the directory where you want to create your DB files, you will not be able to put *.MDF files on a different folder (directory) thant *.LDF files. Which means that after each AppSet restoration you will have to manually move at least the *.LDF or *.MDF file. I think this can be scripted with a T-SQL command... But you will have to do it.
    On a side note, i tried to delete Key #3 (was hoping that it will use key #1 and #2) => This is not working. The AppSet restore will fail (in fact this is SQL Server who will throw an error).
    Will ask my customer to open a case on SAP support, maybe it could be "fixed" one day.

  • SAP Virtual Host installation on windows

    Hi,
      I am trying to Install SAP with virtual host on windows 2003 server.
    Is there any way to create a virtual host name in windows.
    I tried creating Virtual host name in /etc/hosts file and using DNS ,But still not working.
    Regards
    SM.Valavan

    Hi,
    You can execute the below command from DOS
    sapinst.exe SAPINST_USE_HOSTNAME=<hostname>
    Regards,
    SBK

  • SAP BPC 5.1 on VMWare

    Hello,
    Does anybody have experience running SAP BPC 5.1 on a virtual server?
    Thanks,
    Roman

    I have a customer that runs BPC 5.0sp2 on one VM.
    They have about 125 users.
    We have had one major indicent; at a certain point the vm file was using all resources (combination of SQL/w3wp/svchost/dllhost services), a restart didn't help. Couldn't find the problem within 4 hours, then, because of time issues we decided to rebuild the vmfile.
    Before we implemented this we told the customer that when performance issues arise, they are at first responsible for searching and solving the problem.
    In practice, they first shout at us and then they realize that it is mostly caused by other VM-files that run on the same hardware in combination with their own network.
    So my advice is to really discuss this properly with the customer and let them know that using VM is their own responsibility.
    Regards,
    Alwin Berkhout

  • Cannot get Osoft virtual directory object: (SAP BPC 7.5 sp08 issue)

    Hi SDNer
    I am facing a different issue after installing sap BPC 7.5 sp08. i ran server diagnostics when i login with a domain user (domain name\bpc_sysadmin) and i see error message as :
    cannot get Osoft virtual directory object: Automation error the system sould bot find path specified- incorrect
    but when i run the diagnostics after logging in with local user Administratot- all green and its ok.
    can some one through views...
    regards
    Kevin

    Hi,
    Check below 2 threads:
    Error in IIS Configuration while Server Diagostic
    Cannot get OSoft virtual directory object
    Also, make sure that IIS settings are correct. Check SAP note 1532499.
    Thanks
    Sunny

  • Installation of SAP NetWeaver on Windows 2003 Server ( 32 Bit )

    Hello Gurus,
    I am planning installation of SAP Net Weaver - SR2 on Windows Server 2003 ( 32 Bit ) and oracle 10g is my database.
    can anybody guide me from where I can install the software coz in the market place SAP N/W-SR3 is available.
    Is SAP N/W - SR3 is recommeded for Windows 2003 Server ( 32 Bit ).
    Can any body guide me the process & my qurey.
    Thanks & Regards
    Shishir

    Read SAp note Note 1108852 - SAP NetWeaver 7.0 / Business Suite 2005 SR3: Windows
    it says:
    21/MAY/08
    SAP system installation only supported on 64-bit operating systems, except for  dialog instances
    As of SAP NetWeaver 7.0 SR3 and Business Suite 2005 SR3, SAP only supports to install dialog instances on 32-bit operating systems. All remaining SAP system instances (central instance, database instance, central services instance (SCS), ABAP central services instance (ASCS)) must be installed on 64-bit operating systems. Therefore the folder "SAP Systems" is not available on the "Welcome screen", when you start the installation from a installation master DVD for 32-bit.
    You might need to install dialog instances on 32-bit if you want to use 32-bit SAP NetWeaver components, such as Adobe document services. We recommend, however, to first check whether these 32-bit components can run on 64-bit operating systems. If so, we recommend to also use 64-bit systems for these components, including the dialog instance.
    If you want to install a non-productive SAP NetWeaver 7.0 SR3 based system (test systems or development are normally productive systems)  on 32-bit, proceed as follows:
          1. Install a SAP NetWeaver 7.0 SR2 (SAP ERP 2005 SR2, SAP CRM 5.0 SR2 SAP SCM 5.0 SR2, SAP SRM 5.0 SR2) system.
          2. Patch this system to SAP NetWeaver 7.0 SR3 (SAP ERP 6.0, SAP CRM 5.0 SR3, SAP SCM 5.0 SR3, SAP SRM 5.0 SR3).

  • Issue with SAP Authentication in a Windows 2003 64 Bits Server

    Hi Experts
        I have an issue in a Windows 2003 64 Bits Server in CMC when i'm in the authentication section i choose SAP the Role Import works fine and I can see the Users Group from SAP BW but the users don't appear.
        I try the same thing in a Windows 2003 32 Bits with the same parameters and works fine i can see de User Groups and The Users from the same BW Server.
    I Think i could be a problem with the 64 bits server the issue is the users from SAP BW are not imported.
    Regards Marvin Soto.

    Hi Ingo,
                  we have some thing similar issue. can you please help us out.
    We Imported users and in options we selected concurrent and every thing worked fine up to 1 month and then automatically our license key say you have only 2 named users. we have a license key for 100 named users now. do we need to delete all the concurrent users from sap now and we need to re-import them by selecting named in options tab of sap. what is the work around for this. i tested by changing the one of the sap user profile to named instead of concurrent, then i am able to login to infoview using sap credentials but when i open a report its says you don't have enough license to perform this operation. can i know why is this happening.
                Environment:
                                       BOBJ XI 3.1, SUN SOLARIS, SAP INTEGRATION KIT.
    Thanks,
    SK.
    Edited by: Siva Vallabhaneni on May 27, 2009 3:28 PM

Maybe you are looking for