Upgrade R/3 4.7 110 from SQL 2000 to ECC 6.0 /SQL 2005

Dear Experts,
We are currently running R/3 4.7 110 with kernel 640 32 Bit Non Unicode on Windows Server 2000/ MS SQL 2000 Platform. We are planning to Upgrade the same to ECC 6.0 on Windows 2003/ SQL 2005 on New x64 Bit Hardware.
I was earlier planning to Upgrade the OS/DB in first Phase moving the same R/3 4.7 on Windows 2003 Server /MS SQL 2005 and then Upgrade it to ECC 6.0 in second phase. But to my surprise when I checked PAM, I found that R/3 4.7 110 is not at all supported on SQL 2005 ( though R/3 4.6 C is)
Now shall I upgrade it to ECC6.0 First with Windows 2003/SQL 2000 ( Because ECC6.0 is supported with MS SQL 2000)and then move to MS SQL 2005 ?
Thanks
Jitendra Tayal

We had the same issue.
So I checked with SAP.
This was their reply.
'SAP R/3 4.7 Ext 110 is supported on SQL 2005. Please refer to the following notes for further information:'
Note 905634 - Release planning for Microsoft SQL Server 2005
Note 799058 - Setting Up Microsoft SQL Server 2005
Note 899111 - Installing R3 4.7SR1 (47X110) on x64 Windows Platform
Note 151603 - Copying an SQL Server database
So feel free to go ahead.
Thanks.
Carl.

Similar Messages

Please Help!!!!! Problem Migrating from sql 2000 stored procedure to PL/SQL

I have used a tool to convert my sql 2000 stored procedure to Oracle 10g PL/SQL, here is an example
SQL 2000 Stored Procedure
CREATE PROCEDURE [GetEmployees]
AS
Select * from EMPMST ORDER BY emp_name
GO
After Transformation i got 2 files, one was a procedure and other a package
CREATE OR REPLACE PACKAGE GLOBALPKG
AS
     TYPE RCT1 IS REF CURSOR;
     TRANCOUNT INTEGER := 0;
     IDENTITY INTEGER;
END;
CREATE OR REPLACE PROCEDURE GetEmployees
     RCT1 IN OUT      GLOBALPKG.RCT1
AS
BEGIN
     OPEN RCT1 FOR
     SELECT *
     FROM EMPMST
     ORDER BY emp_name;
END;
When i execute the procedure GetEmployees i got this error :
SQL> execute GetEmployees;
BEGIN GetEmployees; END;
ERROR at line 1:
ORA-06550: line 1, column 7:
PLS-00306: wrong number or types of arguments in call to 'GETEMPLOYEES'
ORA-06550: line 1, column 7:
PL/SQL: Statement ignored
Please Help me in debugging this error. Thanks in advance.

As the poster above mentioned you cannot call "GetEmployees" without a parameter.
Note that the procedure declaration has the following line
RCT1 IN OUT GLOBALPKG.RCT1
This means that whenever you want to call the procedure you must pass it a variable of type GLOBALPKG.RCT1
However unless this is merely a homework or learning exercise (i.e. you are not porting the code of a production application) i would strongly recommend that you do not attempt to simply convert the code to PL/SQL.
The reasoning behind this is that Oracle's architecture will be completely different to the source of the original code and if you attempt to simply port the code (especially using an automatic tool) you will almost certainly hit problems.
For example the SQL Server's 2000 code may (should be) be written based on SQL Server's locking strategy. Oracle's locking strategy is completly different if you try to use the same techniques as you do in SQL Server the performance will suffer.
Porting a code or a database schema from one platform to another involves a lot of analysis in order to take advantage of the features of the destination platform.
As I said this may not be important to you depending on why you are attempting a port.
Good Luck.

SQL 2000 ODBC CONNECTION STRING FOR SQL 2008

i have vb 6 application. Database is SQL server 2000.
my connection string is (using odbc driver),
        .ConnectionString = "Driver={SQL Server};SERVER=" & mServer & ";DATABASE=mydb;UID=" & mLogin.Username & ";pwd=" & mLogin.Password & ";"
Now i have tried this application with SQL server express 2008 R2
Can i still keep the old connection string? will there be any problem in future?
(if i have to change then have to change at so many places.....)
I can run application without any problem for now (not changed connection string to new one)
otherwise i have to use ODBC or OLEDB which are,
        .ConnectionString = "Driver={SQL Server Native Client 10.0};SERVER=" & mServer & ";DATABASE=mydb;UID=" & mLogin.Username & ";pwd=" & mLogin.Password & ";"
or
        .ConnectionString = "Provider=SQLNCLI10;SERVER=" & mServer & ";DATABASE=mydb;UID=" & mLogin.Username & ";pwd=" & mLogin.Password & ";"
if i have to change to new connection string Which one is better to use odbc or oledb.
h2007

personally I favor ODBC as it is easy to use sometime. Additionally you can check the link below:
http://social.msdn.microsoft.com/Forums/en/sqlintegrationservices/thread/19e0c306-0be4-46b5-b207-0937931d63a7
cheers!!!
Vatsa
www.objectiveprogramming.com

OS upgrade from windows 2000 to Windows 2003/ 2008

Hi friends,
We are planning to do an OS upgrade of our current production system from windows 2000 to Windows 2003/ 2008.
Can you please refer me to any existing document /Forum link which has a detailed strategy outlaying the activites to be performed for this.
Regards,
Rohit

Hello,
Just upgrading the OS to 2003 should be OK as 640 - 700 kernel is supported on Windows 2003
www.service.sap.com/pam
For 2008 minimum level is 700 SR3 best to do a system copy
SAP on Microsoft Windows:
SAP on Microsoft Windows
regards,
John Feely

Upgrade from SQL 2000 to 2005

In our test environment, we are on 2005 SP01 PL34, and are
upgrading SQL Enterprise Edition from the 2000 to the 2005 SP2 edition.
The SQL upgrade advisor has given some error messages
in relation to SAP tables, as per below. Should we be concerned about
these, or will they have any effect on upgrading from SAP B1 2005 to
2007 versions?
Remove references to undocumented system tables
Many system tables that were undocumented in prior releases have changed or no longer exist; therefore, using these tables may cause errors after upgrading to SQL server 2005.
Affected tables
Object Name : TmSP_GetDbSizeByDrives
Object Type : P
System Table : spt_value
Object Name : TmSP_CheckDiskSpace
The above messages point to SAP stored procedures.

I believe all those SP are temporary SP for you previous upgrade. Therefore. it should be no problem to upgrade your test database first. You have to back up the pre upgrade database anyway, you should be safe.
Thanks,
Gordon

Error while upgrading to 10.1.3.5 from 10.1.3.1

hi
i am trying to upgrade to 10.1.3.5. i ran the bpel upgrade scripts with ORABEL user and it all went fine.
I ran ESB upgrade script (upgrade_10131_10135_oracle.sql) with ORAESB user and i am getting errors.
Below are the errors - Please help.
SQL> Rem DESCRIPTION
SQL> Rem <short description of component this file declares/defines>
SQL> Rem
SQL> Rem NOTES
SQL> Rem <other useful comments, qualifications, etc.>
SQL> Rem
SQL> Rem MODIFIED (MM/DD/YY)
SQL> Rem atusingh 06/20/08 - Backport atusingh_bug-7163503 from
SQL> Rem st_pcbpel_10.1.3.1
SQL> Rem atusingh 06/17/08 - Backport atusingh_bug-7168163 from
SQL> Rem st_pcbpel_10.1.3.1
SQL> Rem atusingh 06/02/08 - Backport atusingh_backport_heartbeat from
SQL> Rem st_pcbpel_10.1.3.1
SQL> Rem atusingh 05/14/08 - Backport atusingh_bug-7017649 from
SQL> Rem st_pcbpel_10.1.3.1
SQL> Rem
SQL>
SQL> Rem SET ECHO ON
SQL> Rem SET FEEDBACK 1
SQL> Rem SET NUMWIDTH 10
SQL> Rem SET LINESIZE 80
SQL> Rem SET TRIMSPOOL ON
SQL> Rem SET TAB OFF
SQL> Rem SET PAGESIZE 100
SQL>
SQL> drop table ESB_message_map;
Table dropped.
SQL> drop table ESB_messages;
Table dropped.
SQL> drop table ESB_group_status;
Table dropped.
SQL> drop table ESB_containerid_lease;
Table dropped.
SQL>
SQL> CREATE TABLE ESB_messages
2 (
3 message_id varchar2(48) PRIMARY KEY, -- unique id for the mess
age
4 system_guid varchar2(48),
5 operation_guid varchar2(48),
6 flow_id varchar2(100),
7 key varchar2(1000), -- modify the size of varchar2 base
d on expected size of key
8 from_system_guid varchar2(48),
9 priority number(3),
10 transactional number(1),
11 correlation_id varchar2(48),
12 error_message varchar2(2000),
13 error_stack varchar2(4000),
14 header blob,
15 data blob,
16 dummy1 varchar2(200),
17 dummy2 varchar2(200),
18 dummy3 varchar2(200)
19 );
Table created.
SQL>
SQL> CREATE TABLE ESB_group_status
2 (
3 group_id varchar2(100), -- group id
4 last_sequence_id varchar2(100), -- sequence id of the last message d
elivered
5 last_received_time timestamp, -- time of the last message delivered
6 error number(1), -- 1 if error
7 lockConId varchar2(100), -- id of the container that locked t
he group
8 lockTime timestamp, -- time locked
9 service_guid varchar2(48), -- guid of service
10 system_guid varchar2(48),
11 destination_system_guid varchar2(48),
12 version number(38,0),
13 dummy1 varchar2(200),
14 dummy2 varchar2(200),
15 dummy3 varchar2(200),
16 PRIMARY KEY(group_id, service_guid)
17 );
Table created.
SQL>
SQL> CREATE TABLE ESB_message_map
2 (
3 id varchar2(48) PRIMARY KEY,
4 service_guid varchar2(48), -- guid of service
5 group_id varchar2(100), -- group id of the message
6 sequence_id varchar2(100), -- sequence id of the message
7 message_id varchar2(48), -- id of the message
8 received_time timestamp, -- time the message was received by the
ESB
9 status number(1), -- message status
10 standard_sequence_id varchar2(100),
11 dummy1 varchar2(200),
12 dummy2 varchar2(200),
13 dummy3 varchar2(200),
14 FOREIGN KEY(message_id) REFERENCES ESB_messages(message_id) on delete c
ascade,
15 CONSTRAINT stnd_reseq UNIQUE(service_guid, group_id, standard_sequence_
id)
16 );
Table created.
SQL>
SQL> create table ESB_containerid_lease (
2 container_id varchar2(100) PRIMARY KEY,
3 renewal_time timestamp
4 );
Table created.
SQL>
SQL> create index resequencer_index1 on ESB_MESSAGE_MAP (STATUS, SERVICE_GUID, G
ROUP_ID, SEQUENCE_ID);
Index created.
SQL>
SQL> -- Create xref_data table if it is not already created by user
SQL> CREATE TABLE XREF_DATA
2 (
3 XREF_TABLE_NAME VARCHAR2(2000) NOT NULL,
4 XREF_COLUMN_NAME VARCHAR2(2000) NOT NULL,
5 ROW_NUMBER VARCHAR2(48) NOT NULL,
6 VALUE VARCHAR2(2000) NOT NULL,
7 IS_DELETED VARCHAR2(1) NOT NULL,
8 LAST_MODIFIED VARCHAR2(100) NOT NULL,
9 LAST_ACCESSED VARCHAR2(100) NOT NULL
10 );
CREATE TABLE XREF_DATA
ERROR at line 1:
ORA-00955: name is already used by an existing object
SQL>
SQL> CREATE INDEX XREF_ROW_NUMBER ON XREF_DATA(ROW_NUMBER);
CREATE INDEX XREF_ROW_NUMBER ON XREF_DATA(ROW_NUMBER)
ERROR at line 1:
ORA-00955: name is already used by an existing object
SQL> CREATE INDEX XREF_VALUE ON XREF_DATA(VALUE);
CREATE INDEX XREF_VALUE ON XREF_DATA(VALUE)
ERROR at line 1:
ORA-00955: name is already used by an existing object
SQL>
SQL> commit;
Commit complete.
SQL> @@upgrade_10134_10135_oracle.sql
SQL> Rem
SQL> Rem $Header: integration/sql/oracle/upgrade_10134_10135_oracle.sql /st_pcbp
el_10.1.3.1/1 2009/03/20 00:47:34 vnuthi Exp $
SQL> Rem
SQL> Rem upgrade_10134_10135_oracle.sql
SQL> Rem
SQL> Rem Copyright (c) 2009, Oracle and/or its affiliates. All rights reserved.
SQL> Rem
SQL> Rem NAME
SQL> Rem upgrade_10134_10135_oracle.sql - <one-line expansion of the name>
SQL> Rem
SQL> Rem DESCRIPTION
SQL> Rem <short description of component this file declares/defines>
SQL> Rem
SQL> Rem NOTES
SQL> Rem <other useful comments, qualifications, etc.>
SQL> Rem
SQL> Rem MODIFIED (MM/DD/YY)
SQL> Rem vnuthi 03/19/09 - Created
SQL> Rem
SQL>
SQL> SET ECHO ON
SQL> SET FEEDBACK 1
SQL> SET NUMWIDTH 10
SQL> SET LINESIZE 80
SQL> SET TRIMSPOOL ON
SQL> SET TAB OFF
SQL> SET PAGESIZE 100
SQL>
SQL>
SQL> ALTER TABLE ESB_FAULTED_INSTANCE add (WSIF_RETRYABLE VARCHAR2(1));
ALTER TABLE ESB_FAULTED_INSTANCE add (WSIF_RETRYABLE VARCHAR2(1))
ERROR at line 1:
ORA-00942: table or view does not exist
SQL> commit;
Commit complete.
SQL>
SQL>
SQL> ALTER TABLE WF_EVENTS
2 ADD ("FQ_PATH" LONG VARCHAR );
ALTER TABLE WF_EVENTS
ERROR at line 1:
ORA-00942: table or view does not exist
SQL>
SQL> DECLARE
2 CURSOR guids_c IS select guid from wf_events;
3 CURSOR steps_c(cguid VARCHAR2) IS select name from (
4 select guid,name,system_guid owner_guid from wf_events
5 where owner_guid is null
6 union
7 select guid,name,owner_guid from wf_events
8 where owner_guid is not null
9 union
10 select guid,name,null owner_guid from wf_systems
11 where guid in (select distinct system_guid from wf_events) )
12 start with guid=cguid connect by guid= prior owner_guid;
13
14
15 path VARCHAR2(32767);
16 sguid wf_events.guid%TYPE;
17
18 BEGIN
19
20 OPEN guids_c;
21 LOOP
22 FETCH guids_c into sguid;
23 EXIT WHEN guids_c%notfound;
24
25 path := '';
26
27 FOR rec IN steps_c(sguid)
28 LOOP
29 path := rec.name || '.' || path;
30 END LOOP;
31
32 path := trim(trailing '.' from path);
33 --dbms_output.put_line('GUID ' || sguid || ' = ' || path );
34
35 update wf_events wf set fq_path = path where wf.guid = sguid;
36 END LOOP;
37 CLOSE guids_c;
38
39 commit;
40 END;
41 /
CURSOR guids_c IS select guid from wf_events;
ERROR at line 2:
ORA-06550: line 2, column 38:
PL/SQL: ORA-00942: table or view does not exist
ORA-06550: line 2, column 21:
PL/SQL: SQL Statement ignored
ORA-06550: line 4, column 59:
PL/SQL: ORA-00942: table or view does not exist
ORA-06550: line 3, column 37:
PL/SQL: SQL Statement ignored
ORA-06550: line 16, column 9:
PLS-00201: identifier 'WF_EVENTS.GUID' must be declared
ORA-06550: line 16, column 9:
PL/SQL: Item ignored
ORA-06550: line 22, column 24:
PLS-00320: the declaration of the type of this expression is incomplete or
malformed
ORA-06550: line 22, column 5:
PL/SQL: SQL Statement ignored
ORA-06550: line 27, column 24:
PLS-00320: the declaration of the type of this expression is incomplete or
malformed
ORA-06550: line 27, column 5:
PL/SQL: Statement ignored
ORA-06550: line 35, column 12:
PL/SQL: ORA-00942: table or view does not exist
ORA-06550: line 35, column 5:
PL/SQL: SQL Statement ignored

got the problem. i am running oraesb as sysdba which i should not do.

Merge Replication from 2012 SQL Server publisher/distributor to 2014 SQL Express subscriber

Hi, I'm having a question about which version to use when running SQL Merge Replication.
In my test enviroment I have a SQL 2012 server running as Publisher and Distributor for my Merge Replication. I have now set up a test client running Win7 with SQL 2014 Express as a subscriber. The subscription initializes and runs perfectly.
But according to the SQL documentation this should not be possible as it states that the subscriber should have a version number equal or lower than the publisher. My subscription client was set ut using SQL-scripting, if I try using the wizard it will just
cause an error message telling that this is not possible since the client has a newer version number. I still not encountered any problems after I set it up using the script with the sp_addmergepullsubscription and sp_addmergepullsubscription_agent procedures.
The roll-out of my solution will start in a few weeks and I now have to decide whether to use 2014 Express or 2012 Express on the clients. Using 2014 Express will save me for a lot of upgades in a year or two. The 2012 SQL Server running as publisher/distributor
will be upgraded to/replaced with a 2014 Server in some few months.
I'm looking for good advices and recommendations for what to choose on the clients, 2012 Express or 2014 Express. Are the any known problems with using 2014 Express as a subscriber to a publisher/distributor running 2012 SQL Server?
All responses are welcome!
Regards, Anders

Hi,
As you understand that a Subscriber to a merge publication can be any version less than or equal to the Publisher version. When you set up a subscription from a publisher to a subscriber using SQL Server Management Studio, you will get error
“The selected Subscriber does not satisfy the minimum version compatibility level of the selected publication.” And you can use T-SQL script to get around this error message.
I would install SQL Server 2012 Express on the clients. Here is the reasons:
1. If you upgrade the publisher to SQL Server 2014, it is still working with SQL Server 2012 on the subscriber.
2. I cannot tell whether there are other potential problems if I choose the later one besides the error message.
Reference:
http://msdn.microsoft.com/en-us/library/ms143699(v=sql.120).aspx
Thanks.
Tracy Cai
TechNet Community Support

Security Permissions from Management Console Not Being Replicated on SQL Server Database

Hi Everyone,
We have been encountering issues with access to Reporting Services for most console users since we upgraded to SCCM 2012 R2. We have observed that since the R2 upgrade, security permissions
that are set in the console are not being replicated on the SQL database. Users/Groups that had access prior to the R2 upgrade are now only able to access Reports via the web interface. All new users/groups are not able to get access at all.
We are not sure what the problem could be and would appreciate any guidance.
We have tried the following without success:
Manually adding new users/groups to the database
Reinstalling the the Reporting Service point and Reporting Service, Removing all of the security groups from the console and from the database, and Adding the security groups back
to the console.
Our current environment:
SCCM 2012 R2
1 Site
Primary Site:
OS: Server 2008 R2
Roles: Site Server / Software Update Point / Management
Point
SQL Server
OS: Server 2008 R2
SQL Version: Microsoft SQL Server 2008 R2
Roles: Site Database Server / Reporting Services Point

Thanks for your feedback.
Permissions
We have two main types of users: Full Administrators and local departmental IT administrators. (Local IT Admins only have full control over their own departmental collections. They have Read/Add to All Systems.)
The only account that's currently able to run Reports from both the console and web is the admin account used to perform the R2 upgrade.
Full Administrator
Role: Full Administrator
Scope: All instances of the objects that are related to the assigned security roles.
Local Departmental Administrator
Role: Full Administrator & Read/Add
Scope: Main Departmental Collection (Full Admin) & All Systems, All Users, and All User Groups (Read/Add)
Report Service Execution
On the database, we have tried assigning the Report Service Execution Account to the built-in Network Service Account, Local Service Account, and to a separate AD role account.
Error Messages
Console: We are able to select reports from the Console however nothing appears when we click on Run.
Web: Generating Reports from the Web works for only the Full Administrators. Nothing appears for a Local Departmental Admin.
This is a partial output from srsrp.log:
Set configuration   SMS_SRS_REPORTING_POINT   3/10/2015 2:28:05 PM   2588 (0x0A1C)
Check state   SMS_SRS_REPORTING_POINT   3/10/2015 2:28:05 PM   2588 (0x0A1C)
Check server health.   SMS_SRS_REPORTING_POINT   3/10/2015 2:28:05 PM   2588 (0x0A1C)
Successfully created srsserver   SMS_SRS_REPORTING_POINT   3/10/2015 2:28:05 PM   2588 (0x0A1C)
Reporting Services URL from Registry [http://132.205.120.154/ReportServer/ReportService2005.asmx]   SMS_SRS_REPORTING_POINT   3/10/2015 2:28:05 PM   2588 (0x0A1C)
Reporting Services is running   SMS_SRS_REPORTING_POINT   3/10/2015 2:28:05 PM   2588 (0x0A1C)
Retrieved datasource definition from the server.   SMS_SRS_REPORTING_POINT   3/10/2015 2:28:05 PM   2588 (0x0A1C)
[SCM-SQL.concordia.ca] [CM_SCM] [ConfigMgr_SCM] [SCM-SQL.CONCORDIA.CA]   SMS_SRS_REPORTING_POINT   3/10/2015 2:28:05 PM   2588 (0x0A1C)
[MSSQLSERVER] [1] [] [CONCORDIA\SVC-SCM_REPORT]   SMS_SRS_REPORTING_POINT   3/10/2015 2:28:05 PM   2588 (0x0A1C)
[1] [0]   SMS_SRS_REPORTING_POINT   3/10/2015 2:28:05 PM   2588 (0x0A1C)
Confirmed version [10.50.2811.0] for the Sql Srs Instance.   SMS_SRS_REPORTING_POINT   3/10/2015 2:28:05 PM   2588 (0x0A1C)
Retrieved datasource definition from the server.   SMS_SRS_REPORTING_POINT   3/10/2015 2:28:05 PM   2588 (0x0A1C)
Updating data source {5C6358F2-4BB6-4a1b-A16E-8D96795D8602} at ConfigMgr_SCM   SMS_SRS_REPORTING_POINT   3/10/2015 2:28:05 PM   2588 (0x0A1C)
Loading localization resources from directory [E:\SMS_SRSRP\SrsResources.dll]   SMS_SRS_REPORTING_POINT   3/10/2015 2:28:05 PM   2588 (0x0A1C)
Looking for 'English (United States)' resources   SMS_SRS_REPORTING_POINT   3/10/2015 2:28:05 PM   2588 (0x0A1C)
Looking for 'English' resources   SMS_SRS_REPORTING_POINT   3/10/2015 2:28:05 PM   2588 (0x0A1C)
Found resources for 'English'   SMS_SRS_REPORTING_POINT   3/10/2015 2:28:05 PM   2588 (0x0A1C)
Confirmed the configuration of SRS role [ConfigMgr Report Users].   SMS_SRS_REPORTING_POINT   3/10/2015 2:28:06 PM   2588 (0x0A1C)
Confirmed the configuration of SRS role [ConfigMgr Report Administrators].   SMS_SRS_REPORTING_POINT   3/10/2015 2:28:06 PM   2588 (0x0A1C)
Error retrieving users - [The EXECUTE permission was denied on the object 'spGetReportUsers', database 'CM_SCM', schema 'SCCM_Rpt'.].   SMS_SRS_REPORTING_POINT   3/10/2015 2:28:06 PM   2588 (0x0A1C)
Error retrieving users - [The EXECUTE permission was denied on the object 'spGetReportUsers', database 'CM_SCM', schema 'SCCM_Rpt'.].   SMS_SRS_REPORTING_POINT   3/10/2015 2:28:06 PM   2588 (0x0A1C)
Confirmed the security policy for folder [/].   SMS_SRS_REPORTING_POINT   3/10/2015 2:28:06 PM   2588 (0x0A1C)
Error retrieving users - [The EXECUTE permission was denied on the object 'spGetReportUsers', database 'CM_SCM', schema 'SCCM_Rpt'.].   SMS_SRS_REPORTING_POINT   3/10/2015 2:28:06 PM   2588 (0x0A1C)
Error retrieving users - [The EXECUTE permission was denied on the object 'spGetReportUsers', database 'CM_SCM', schema 'SCCM_Rpt'.].   SMS_SRS_REPORTING_POINT   3/10/2015 2:28:06 PM   2588 (0x0A1C)
Confirmed the security policy for folder [/ConfigMgr_SCM].   SMS_SRS_REPORTING_POINT   3/10/2015 2:28:06 PM   2588 (0x0A1C)
Error retrieving users - [The EXECUTE permission was denied on the object 'spGetReportUsers', database 'CM_SCM', schema 'SCCM_Rpt'.].   SMS_SRS_REPORTING_POINT   3/10/2015 2:28:06 PM   2588 (0x0A1C)
Error retrieving users - [The EXECUTE permission was denied on the object 'spGetReportUsers', database 'CM_SCM', schema 'SCCM_Rpt'.].   SMS_SRS_REPORTING_POINT   3/10/2015 2:28:06 PM   2588 (0x0A1C)
Confirmed the security policy for folder [/ConfigMgr_SCM/Asset Intelligence].   SMS_SRS_REPORTING_POINT   3/10/2015 2:28:06 PM   2588 (0x0A1C)
Error retrieving users - [The EXECUTE permission was denied on the object 'spGetReportUsers', database 'CM_SCM', schema 'SCCM_Rpt'.].   SMS_SRS_REPORTING_POINT   3/10/2015 2:28:06 PM   2588 (0x0A1C)
Error retrieving users - [The EXECUTE permission was denied on the object 'spGetReportUsers', database 'CM_SCM', schema 'SCCM_Rpt'.].   SMS_SRS_REPORTING_POINT   3/10/2015 2:28:06 PM   2588 (0x0A1C)

Custom DTS package migration from BPC 4.2 ,SQL 2000 to BPC 7.0 M , SQL 2005

Is there any changes required in the custom dts package when migration from BPC 4.2 , sql 2000 Environment to bpc 7.0 , SQL 2005/2008 Environment.
or
Please suggest process for migrating custom dts package from BPC 4.2 ,SQL 2000 Envirnment to BPC 7.0 ,SQL 2005/2008 Environment

When you say "custom dts package" that can mean many different things. What type of customization has been done?
There are a few BPC-related features which changed from 4.2, which must be manually adjusted, if you're using those features.
But SQL itself also changed dramatically in moving from SQL 2000 to 2005. So if your customer's packages are heavily customized around SQL 2000, this may require substantial re-work.
The only migration process for custom DTS packages -- that I'm aware of -- is to use the SQL 2005 migration tool in SSIS, see how much it messed up, and then fix everything else that's still broken.
But there also may be opportunities to improve the package overall. SQL 2005 has a lot of great new features in SSIS, over what was there in SQL 2000.
I haven't started working with SQL 2008 yet, so I can't say what complexity there is in upgrading DTS packages from 2005 to 2008. From what I read in the BPC 7 release notes, it sounds like it's a very minor upgrade, compared to the jump from 2000 to 2005.

Upgrade from 4.6c to ECC 5

Hi experts ,
One of our clients have implemented SAP 4.6c few years ago. Now they are facing a lots of problems. Basically these problems arises due to some cofiguration faults. They now want to upgrade their SAP version and as well as want to stable their whole SAP system. So please suggest me what will be the proper approach to do the upgradation as well as stable their system both functionally and technically. Please tell me in details
thanks and regards

Hi Pratik,
1. First of all check what is the OS and hardware that client is working on.
I mean check if the systems are on 32bit hardware or 64 bit.
If you need to upgrade the hardware then please follow the OSS note 960769.
2. Check whats the database.
If oracle lower version like 8i then upgrade it to 9i and then upgrade from 9i to 10g.
If SQL 2000 then have the clean installation of SQL 2005.
3. Then go ahead with the upgrade. Again you would need to check if client wants to have combined upgrade and unicode conversion or upgrade first and then unicode conversion.
Please follow the link mentioned below and also go through the installation guide.
https://wiki.sdn.sap.com/wiki/display/HOME/ERP2005+Upgrade
and get the appropriate upgrade guides from http://service.sap.com/instguides
Reward if helpful.
Regards,
Imran
Edited by: Imran Khan on Feb 20, 2008 12:34 PM

Upgrade windows 2000 t o windows 2005 and sql 2000 to sql 2005

Dear People,
i have not actually done any upgradestill now, i have task where i need to upgrade existing sap system.The sap has already been upgraded, now my task is to upgrade operating system and database
requirement:
windows 2000 to windows 2003
sql 2000 to sql 2005
the above should be done by the procedure recommended by sap only, so im wondering where i can find the information and tools for uprading both O/S and DB.
Help
Raj

I personally would not do a Windows upgrade, Windows can be very picky when it comes to 3rd party SCSI/FC drives you may experience bluescreens during the update after the second boot etc.
I would backup the system and install the operating system from scratch and do a system copy instead.
For your database upgrade, there's a guide at
http://service.sap.com/instguides
--> Other documentation
--> Database upgrades
Markus

Restoration at sql 2005 from sql 2000 backup.

Hi experts,
Is it possible to restore a backup taken from sql 2000 database to sql 2005 database?
And how about attaching datafiles of sql2000 into sql 2005 server?
Thanks and Regards,
Amit Jana.

> Is it possible to restore a backup taken from sql 2000 database to sql 2005 database?
Yes its possible.
> And how about attaching datafiles of sql2000 into sql 2005 server?
Same method of attach/deattach.
But recommanded you first install 2000 instance restore database and do inplace sql 2005 upgrade.
Why you can't follow recommanded mothed ?
Regards,
Nikunj Thaker

Upgrade from Windows 2000 to Windows 2003

Dear all,
We are upgrading our CRM Sever from Versio 4.0 to CRM 5.0. Do we need to upgrade our Operating system from Windows 2000 to Windows 2003?
Kind regards,
Raquel Mendoza

Hi Eric,
I have checked the link. Does this mean that I need to upgrade my OS to WINDOWS SERVER 2003 64bit?
> Released for CRM Server Database Platforms SAP KERNEL 7.00 64-BIT MS SQL SERVER...
Released Database Version Operating System
MS SQL SERVER 2000 WINDOWS SERVER 2003/X64 64BIT
MS SQL SERVER 2000 IA64 WINDOWS SERVER 2003/IA64 64BIT
MS SQL SERVER 2005 IA64 WINDOWS SERVER 2003/IA64 64BIT
MS SQL SERVER 2005/X86_64 WINDOWS SERVER 2003/X64

Upgrade SQL 2000 to SQL 2005 --- schema conversion error

Hi, I execute an upgrade from MSSQL 2000 to MSSQL 2005 and everything executed succesfully. Then i download the "SAP Tools for MSSQL Server"
to execute the schema conversion of the database. But i get an error when a step tries to create the stored procedures in the db. Specifically i get the error in the sap_blocked_procccess store procedure with the following error:
ERROR 2006-12-07 10:19:57
FCO-00011 The step ExeProcs with step key |SAPMSSTOOLS|ind|ind|ind|ind|0|0|MssSysCopy|ind|ind|ind|ind|4|0|MssProcs|ind|ind|ind|ind|4|0|ExeProcs was executed with status ERROR .
ERROR 2006-12-07 10:19:57
MDB-05053 Errors when executing sql command: <p nr="0"/> If this message is displayed as a warning - it can be ignored. If this is an error - call your SAP support.
INFO 2006-12-07 10:30:00
An error occured and the user decided to retry the current step: "|SAPMSSTOOLS|ind|ind|ind|ind|0|0|MssSysCopy|ind|ind|ind|ind|4|0|MssProcs|ind|ind|ind|ind|4|0|ExeProcs".
ERROR 2006-12-07 10:30:29
FCO-00011 The step ExeProcs with step key |SAPMSSTOOLS|ind|ind|ind|ind|0|0|MssSysCopy|ind|ind|ind|ind|4|0|MssProcs|ind|ind|ind|ind|4|0|ExeProcs was executed with status ERROR .
I didn't find any note or something else.
Do you have any idea about this problem?
Best Regards,
Thanasis

Hello,
please ensure that the Database compatibility level for all databases is 90 by
running
exec sp_dbcmptlevel 'master',90
exec sp_dbcmptlevel 'model',90
exec sp_dbcmptlevel 'msdb',90
exec sp_dbcmptlevel 'tempdb',90
exec sp_dbcmptlevel 'EA5',90
Then rerun the STM tools.
Regards
Clas

Unable to Connect to SQL 2000 Instance from Windows Server 2012 environment

We have a windows server (TEST) 2012 environment , where our test SQL Server 2012 instance is hosted.
We have a different (DEV) Server (windows 2000) where a SQL Server 2000 instance is present.
When I RDP to our Windows Server 2012 box, I cannot connect to the SQL 2000 server instance from SQL Management Studio. (whereas I can connect to
the same server from my local machine which has windows 7 and SQL 2012 installed).
This is the error i see -
"A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 - The specified network name
is no longer available.) (.Net SqlClient Data Provider)"
When run from SQL Agent Service from TEST (A Job which tries to connect to that SQL 2000 instance to read some data using SSIS) , we get the following
error -
An OLE DB record is available. Source: "Microsoft OLE DB Provider for SQL Server" Hresult: 0x80004005 Description: "[DBNETLIB][ConnectionRead
(recv()).]General network error. Check your network documentation.".
The same SSIS package runs successfully from my local machine.
Please, could someone advice how to resolve this situation?

Thanks Olaf.
Its just that we have legacy systems here in our company, who, for some reason haven't upgraded their older infrastructure, whereas they have set up new Windows 2012/SQL 2012 environments for the newer sql instances where they want to transition to !
Not sure what the solution is honestly. It is affecting our timelines now. The infrastructure team needs to take a decision now, as to what to do.
I do have to add, we were able to connect to these "older" servers from our Windows 7 client machines which have SQL 2012 - both from SQL management studio & SSIS (using OLE-DB Provider for SQL Server).

Upgrade R/3 4.7 110 from SQL 2000 to ECC 6.0 /SQL 2005

Similar Messages

Maybe you are looking for