MSSQL 2005 SP3 installation

Hi
I'm currently looking to upgrade our SQL from 2005 SP2 to SP3 on a windows cluster server (server 2003). I've never done any 'hands on' with DB upgrades.
Any help/advice would be greatly appreciated

Hello,
Take cluster and db offline.
Then apply SP3 use account that is member of local admin
group on the server.
Normally <sid>adm
SAP Note 62988 [Service packs for Microsoft SQL Server]
regards,
John Feely

Similar Messages

The acount information could not be verified - SQL 2005 SP3 installation on Windows 2008 R2 Failover Cluster

Hi,
We have a problem when we are trying to install SQL SP3 on SQL 2005 cluster.
The problem is described bellow:
We installed a new Windows 2008 R2 x64 failover cluster with two nodes.
As a next step we installed SQL 2005 Enterprise edition x64 on this failover cluster. We have finished the installation without problems. After SQL installation we are trying to install SQL SP3 . We have logged on using a domain administrator account and
we start the installation of SP3 with that user. In authentication mode screen the test gives a success status using either domain administrator-windows authentication or sa-sql authentication. On remote user account screen, when we give the domain
administrator account we get the message "the account information could not be verified. Press ok to return to authentication mode screen to determine the reason for failure".
We have tried to give the SQL services startup user on remote user account screen but the error is the same.
the domain administrator account exists on security logins of SQL with sysadmin rights.
Can someone help?
Thanks.

Hi StelioMavro,
According to your error message, when you install SQL Server 2005 SP3 in your failover cluster, we need to verify if there was other instance that had been removed and the installation did not pass the login check. I recommend you use windows authentication
instead of SQL Server authentication when applying SP3. And the windows account used to run the SP3 setup program must have administrator privileges on the computer where SP3 will be installed.
For more information about how to install SQL Server 2005 SP3 in failover cluster, you can review the following article.
http://www.sqlcoffee.com/Tips0007.htm
Regards,
Sofiya Li
Sofiya Li
TechNet Community Support

Getting error while installing MSSQL 2005 SP2 Windows Server 2008 Service Pack 1

Hi,
We are getting error while we are installing MSSQL 2005 SP2.
It gives me the following error
No Qualifying Product
===================
This machine does not have a product that matches this installation package.
I am pretty new to MSQL. Any help to solve this is much more appreciated.

Hello,
It seems you downloaded Service Pack 2 for SQL Server 2005 alone, that download does not install a SQL Server 2005 instance.
You might have to download and install SQL Server 2005 and then proceed to apply service packs related to that version of SQL Server.
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Can SBO-COMMON database be re-attached after Reinstalling MSSQL 2005

Hi All,
I encountered collation issue. The MSSQL Server Collation is incorrectly indicated when upgrade from 2005B to 8.8 was performed. (the correct one should be SQL_Latin1_General_CP1_CI_AS instead of Latin1_General_CI_AS. But my various company databases are correctly stated as SQL_Latin1_General_CP850_CI_AS (as required by SAP B1).
Now, I am considering creating a new SQL Instance with the correct collation, then use the SBO Upgrade Server to create the SBO-COMMON and re-direct the License Server to the new instance. But all my AddOns requires for re-installation.
My next alternative is to uninstall MSSQL 2005 and re-install with the correct collation. But I am wondering if the backup SBO-COMMON can be used. Also, will the installed AddOns prompts for re-installation?
I have checked against SAP Note 987436. is this the only lifeline?
These solutions will required certain amount of downtime from the customer. Is there a cleaner way out of this?
Please help.
Regards
Jessie Ng

Hi,
Some of our B1 customers have encountered the wrong collation settings. Here are the problems they've got :
1. When trying to use any functionality of Drag & Relate, the following error message will be displayed: 'No matching record found'.
2. When runing "Sales\Purchase analysis report" for Business Partner, the report might not retrieve any results eventhough it should.
Here is the solution from SAP note:
Collation Settings of MSSQL Server 2005 or 2008
Symptom
When defining the wrong collation during manual installation of MSSQL Server 2005 or MSSQL 2008, in certain situations it might cause functional problems. Examples:
1. When trying to use any functionality of Drag & Relate, the following error message will be displayed: 'No matching record found'.
2. When runing "Sales\Purchase analysis report" for Business Partner, the report might not retrieve any results eventhough it should.
Other terms
MSSQL 2005, MSSQL 2008, SQL server, documentation, collation, Drag & relate, drag and relate, collation settings, collation setting, SQL 2005, SQL 2008
Reason and Prerequisites
Consulting Note
Solution
The latest version of any documentation can be found at http://service.sap.com/smb/sbo/documentation.
Please make sure to choose collation setting of: SQL_Latin1_General_CP1_CI_AS
when installing MSSQL 2005 / 2008 Server.
In order to check what the collation is set to in your server, please run the following query:
Collation of your Server:
select SERVERPROPERTY ('collation')
(This query gets the collation settings of MSSQL Server's System Database "Master")
Expected answer : SQL_Latin1_General_CP1_CI_AS
In case you have already installed the MSSQL 2005 or 2008 Server with any collation other than SQL_Latin1_General_CP1_CI_AS, please follow the steps below:
Change your server collation to SQL_Latin1_General_CP1_CI_AS.
You can find Microsoft's instructions for changing an SQL server collation here:
http://msdn2.microsoft.com/en-us/library/ms179254.aspx
Please note that collation settings of Database "Master" needs to be changed only. All SAP Business One Databases must not be changed! These must remain on SQL_Latin1_General_CP850_CI_AS.
If you need any clarifications with this process please refer to an Expert Empowerment Session "SQL 2005 Server Collation settings" at https://websmp203.sap-ag.de/~sapidb/011000358700000050892007E/ or http://service.sap.com/smb/sbo/support -> Archive: Empowerment Sessions.
If you have any Servicepack for MSSQL Server installed, but the Servicepack is not included into your DVD MSSQL Server, do as follows:
1. Deinstall Servcicepack
2. Change Collation Settings as per Expert Empowerment Session
3. Install Servicepack again
JimM

SAP IQ 16 remote procedure to MsSQL 2005 error.

Hi all,
    I've in IQ a remote procedure that call via RPC an old MsSQL 2005 stored procedure.
In my old installation with IQ 12.7 ESD 4 all works well and I don't report any issues.
Actually with the new IQ 16.0 SP08 I've the following strange behaviours.
ERROR 1) When I call the remote procedure from IQ using SAP Interactive SQL all works well if I run the client from a remote host. I mean from an host which is not the server where IQ engine is running. If I execute the same call (always from SAP Interactive SQL) on the IQ engine server the following error is reported:
There was an error reading the results of the SQL statement.
The displayed results may be incorrect or incomplete.
Cursor not in a valid state
SQLCODE=-853, ODBC 3 State="24000"
Cursor not in a valid state
SQLCODE=-853, ODBC 3 State="24000"
Server 'SVR_PRODOTTI': [Microsoft][ODBC SQL Server Driver]Function
sequence error
SQLCODE=-660, ODBC 3 State="HY000"
ERROR 2) I've the following scenario:
     a.     I call a remote procedure (always the MsSQL 2005 remote procedure described above) inside a standard IQ stored procedure
     b.     the remote procedure fill a remote table with some data
     c.     in IQ after that the remote procedure is executed I want to get the produced data in IQ via proxy table
Looking at MsSQL side I note that step (a) and (b) are executed, but when step (c) start running it remains blocked by the session that had run step (a and b) even if they are already finished. Look at the following extraction of session state by MsSQL side.
SPID Status Login HostName     BlkBy DBName Command CPUTime      DiskIO LastBatch ProgramName       SPID   REQUESTID
177 SUSPENDED usr     IQ_SERVER 287    master EXECUTE            0        0        06/19 17:31:38 Sybase IQ 177    0
287 sleeping usr     IQ_SERVER    .    master AWAITING COMMAND    9829 153149       06/19 17:31:38 Sybase IQ 287    0
SPID = 287 (remote procedure call)
RPC Event 0      sp_remote_procedure;1
SPID = 177 (proxy table access)
Language Event 0      SELECT .... FROM .... t1
Environment details:
IQ -> SAP IQ 16.0 SP08 on Win 2012 R2 server (64 bit)
MSSQL -> MsSQL 2005 SP 2 32 bit Enterprise on Win 2003 server (32 bit)
Do you have any suggestions about this strange behaviours?
Best regards,
Stefano

Hi Tayeb,
    thank you for your suggestions, following some improvement and details about my errors.
ERROR 1) [SOLVED]
In SAP Interactive SQL: Tools -> Options -> SAP Sybase IQ
The problem appear only if "Result processing" options are configured as:
"Show results from the last statement" --> ON
"Show only the first result set" --> ON
..hereafter I report the image that show the configuration that caused error.
Any other configuration of these two parameters doesn't show any problem.
ERROR 2) [already present]
I checked the IQ 16 SP08 doc and as you reported MsSQL 2005 is not listed in RPC certified systems.
I checked also the old IQ 12.7 ESD 4 (the version from which I want to migrate and where all works fine every day) doc and the same statement was reported. So not even in 12.7 release MsSQL RPC call seems to be certified, even if it still withou any problem.
After some other tests tracing also different debugging mode (-zo and -zr) I share the following result.
I tried the following use cases.
Note that "rem_mssql_TARGET" sp insert data in a local table on MsSQL which is selected by IQ via proxy "pr_DELTA_IQ".
[TEST A] - RDP via select
    select
      @max_date = RetDate,
      @error = RetCode
    from
      DBA.rem_mssql_TARGET('2014-06-20 15:00:00')
insert into DBA.DELTA_IQ
FIELD_1,
FIELD_2
                       location 'TARGET_DB.TARGET_DB'
    select
FIELD_1,
FIELD_2
    from DBA.pr_DELTA_IQ
PROBLEM: on MsSQL all remains blocked, because proxy table extraction is blocked by remote procedure execution that result running.
If I kill the remote procedure session from MsSQL, IQ engine shutdown itself without any messages.
No data is inserted in DBA.DELTA_IQ.
[TEST B] - RDP via exec
exec DBA.rem_mssql_TARGET ('2014-06-20 15:00:00')
insert into DBA.DELTA_IQ
FIELD_1,
FIELD_2
                       location 'TARGET_DB.TARGET_DB'
    select
FIELD_1,
FIELD_2
    from DBA.pr_DELTA_IQ
PROBLEM: MsSQL doesn't report any blocking session.
IQ return the following message and the IQ server doesn't shutdown itself.
SQLCODE=-706, ODBC 3 State=“HY000”
Remote server does not have the ability to support this statement
Anyway all is rollbacked an no data is inserted in DBA.DELTA_IQ.
Do you have any other hints about it?
Thank you and regards,
Stefano

How to do a system copy in MSSQL 2005

Hi,
Pls let me know how to do a System Copy for ECC6 in MSSQL 2005
Regards,
Manjunath B

Hi Maria / Manjunath, you can follow the instruction at http://service.sap.com/msplatforms -> SQL Server -> Upgrade to and Installation of SQL Server 2005.
Also you can go to http://service.sap.com/instguides -> SAP Netweaver 7.0 -> Installation -> System Copy for SAP Systems Based on NW 7.0 SR1 ABAP or System Copy for SAP Systems Based on NW 7.0 SR2 ABAP
If you have any other question, please post it.
Regards,
Darwin Castillo
SAP Netweaver System Administrator
Edited by: Darwin Castillo on Mar 9, 2008 11:49 AM

BPC 5.1 SP11 with SQL SERVER 2005 SP3

Hi all,
i have a BPC 5.1 SP11 single-server installation.
I know the DB Server prerequisite is Microsoft SQL Server 2005 SP2 and cumulative update package 8.
SQL Server 2005 SP3 is supported?
is there any document about compatibility?
have i install SP3 before or after BPC Installation?
thanks

HI Paolo,
SQL Server 2005 SP3 is supported with SAP BPC 5.1 SP3 or any other later version.
We already installed for few customers SP3 and this patch fix bugs into SSAS and also improve some performances regarding SSAS.
So the recommendation will be to apply this patch in your environment because it will bring just benefits.
If you have multiserver installation remmeber that you have to apply the patch in all servers not just into Database server.
Regards
Sorin Radulescu

SQL server 2005 SP3 can run SAP B1 2005A SP01 PL51

Hi All,
I could successfully install SAP B1 2005A SP01 PL51 in the SQL server 2005 SP3.
In this link:
http://service.sap.com/smb/sbo/platforms
you won't find it such info.
Why I upgrade, it is caused by the printing error issue using citrix.
Anyone of you that have problem after run the B1 on that SQL, pls share.
Someone who need webex file that shows the install process can request it to me. Let me know.
Rgds,

Hi Arshdeep,
Thx for your reply. I just wonder why SAP did not inform the availability SP3 from Microsoft and the explanation about the inapplicable of SP3 for SAP B1 in the B1 platform link.
I have tested without using any steps and any other procedures. Practice is a good lesson to learn for me. Nevertheless, one concern from modern customers are the compatibility or adaptibility of SAP B1 to Microsoft product especially SQL since it is one of database platform.
Old-fashioned customer will disregard that because they will think as long as my SAP B1 and SQL server still run well, I don't care..
Rgds,

UpGrade failed 9.3.4294 (2005 SP3 PatchSet 9) to 10.50.1600.1.

Hi, I've tried an UpGrade from 9.3.4294 (2005 SP3 PatchSet 9) to 10.50.1600.1. (SAP media ID 51039339)
The setup failed by execution of 'sqlagent100_msdb_upgrade.sql' with error code 574.
I found the following KB articele http://support.microsoft.com/kb/960781 and this blog http://blogs.msdn.com/b/psssql/archive/2008/09/10/upgrade-for-sql-server-2008-can-fail-if-you-have-renamed-the-sa-account.aspx.
I could start the service and execute the proposed statement to my named instance as followes:
...Binnsqlservr.exe" -sSAPQPT -c -f -T 3608
<-- message if sqlcmd is active:
2011-05-20 16:13:46.88 spid51 Starting up database 'QPT'.
2011-05-20 16:13:47.89 spid51 CHECKDB for database 'QPT' finished without e
rrors on 2011-05-15 09:00:06.870 (local time). This is an informational message
only; no user action is required.
sqlcmd -S tpzsqp01SAPQPT -E -A -Q"alter login <sys-admin> with name = sa"
<-- this gives no feedback to the console...
After this I've used the Repair function of the SQL 2008 setup, but it failed on the same scipt 'sqlagent100_msdb_upgrade.sql'.
I've also tried to change the sa password
sqlcmd -S tpzsqp01SAPQPT -E -A -Q"ALTER LOGIN sa WITH PASS
WORD = 'xxx' UNLOCK;"
But I'm not able to connect to the server via TCP
C:Windowssystem32>sqlcmd -U sa
Password: HResult 0x274D, Level 16, State 1
TCP Provider: No connection could be made because the target machine actively re
fused it.
Sqlcmd: Error: Microsoft SQL Native Client : An error has occurred while establi
shing a connection to the server. When connecting to SQL Server 2005, this failu
re may be caused by the fact that under the default settings SQL Server does not
allow remote connections..
Sqlcmd: Error: Microsoft SQL Native Client : Login timeout expired.
At the moment I don't know what is wrong with the master db and why the setup can not connect with the sa account... we did not change this account in the past?! I've done the setup and this failed with the same error as described in http://support.microsoft.com/kb/960781. I've followed up this KB article but it did not solve the problem. The problem is still available.
Error messages by setup are:
Detail.txt
2011-05-20 10:26:03 Slp: Error result: -2061893608
2011-05-20 10:26:03 Slp: Result facility code: 1306
2011-05-20 10:26:03 Slp: Result error code: 24
SQLServer_ERRORLOG_2011-05-20T09.47.03.txt
cript level upgrade for database 'master' failed because upgrade step 'sqlagent100_msdb_upgrade.sql' encountered error 574, state 0, severity 16. This is a serious error condition which might interfere with regular operation and the database will be taken offline. If the error happened during upgrade of the 'master' database, it will prevent the entire SQL Server instance from starting. Examine the previous errorlog entries for errors, take the appropriate corrective actions and re-start the database so that the script upgrade steps run to completion.
Detailed results:
Feature: Database Engine Services
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Failed: see details below
Configuration error code: 0x4BDAF9BA@1306@24
Configuration error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Configuration log: C:Program FilesMicrosoft SQL Server100Setup BootstrapLog20110520_164101Detail.txt
Feature: SQL Server Replication
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Failed: see details below
Configuration error code: 0x4BDAF9BA@1306@24
Configuration error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Configuration log: C:Program FilesMicrosoft SQL Server100Setup BootstrapLog20110520_164101Detail.txt
Feature: Full-Text Search
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Failed: see details below
Configuration error code: 0x4BDAF9BA@1306@24
Configuration error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Configuration log: C:Program FilesMicrosoft SQL Server100Setup BootstrapLog20110520_164101Detail.txt
Edited by: René Schulz on May 24, 2011 9:23 AM

for further ideas with trace flag -T3601; the upgrade script seems to have a problem with RECONFIGURE ??? :
/* DMF Post-upgrade steps */
-- >>> CTP5 -> CTP6 Upgrade
-- Restoring previously saved data and converting TargetSets to ObjectSets
IF (OBJECT_ID('dbo.dmf_upgrade', 'U') IS NOT NULL)
BEGIN
BEGIN TRANSACTION
-- Restore policies
SET IDENTITY_INSERT dbo.syspolicy_policies_internal ON
INSERT dbo.syspolicy_policies_internal (policy_id,name,condition_id,root_condition_id,date_created,execution_mode,policy_category_id,schedule_uid,description,help_text,help_link,is_enabled,job_id,created_by,modified_by,date_modified)
SELECT policy_id,name,condition_id,root_condition_id,date_created,execution_mode,policy_category_id,schedule_uid,description,help_text,help_link,is_enabled,job_id,created_by,modified_by,date_modified
FROM msdb.dbo.tmp_syspolicy_policies_internal
SET IDENTITY_INSERT dbo.syspolicy_policies_internal OFF
-- Restore Health state
SET IDENTITY_INSERT dbo.syspolicy_system_health_state_internal ON
INSERT dbo.syspolicy_system_health_state_internal (health_state_id,policy_id,last_run_date,target_query_expression_with_id,target_query_expression,result)
SELECT * FROM msdb.dbo.tmp_syspolicy_system_health_state_internal
SET IDENTITY_INSERT dbo.syspolicy_system_health_state_internal OFF
-- Restore Execution history
SET IDENTITY_INSERT dbo.syspolicy_policy_execution_history_internal ON
INSERT dbo.syspolicy_policy_execution_history_internal (history_id,policy_id,start_date,end_date,result,is_full_run,exception_message,exception)
SELECT * FROM msdb.dbo.tmp_syspolicy_policy_execution_history_internal
SET IDENTITY_INSERT dbo.syspolicy_policy_execution_history_internal OFF
SET IDENTITY_INSERT dbo.syspolicy_policy_execution_history_details_internal ON
INSERT dbo.syspolicy_policy_execution_history_details_internal (detail_id,history_id,target_query_expression,target_query...
2011-05-23 14:03:53.29 spid7s Configuration option 'show advanced options' changed from 1 to 1. Run the RECONFIGURE statement to install.
2011-05-23 14:03:53.29 spid7s Configuration option 'show advanced options' changed from 1 to 1. Run the RECONFIGURE statement to install.
2011-05-23 14:03:53.30 spid7s Error: 574, Severity: 16, State: 0.
2011-05-23 14:03:53.30 spid7s CONFIG statement cannot be used inside a user transaction.
2011-05-23 14:03:53.30 spid7s Error: 912, Severity: 21, State: 2.

The tables are not listed in table browser (Designer) MS SQL 2005 SP3

Database: SQL 2005 SP3, using ODBC Connection
Database name: Test_7.6_Reporting
Business Objects XI3.1 SP2
When I open the table browser, I see all my databases listed.
If I expand these I see three folders - Information_Schema, dbo and Sys, it doesn't show anything after i expand dbo.
I need to know how to get these tables to show.
Please advice. Thanks!

Hi BK,
This seems odd. All I can think of is that there may be a security issue. Maybe it doesn't register you as dbo. Check into the possible security differences between you and a user who can see those tables under dbo.
Thanks!
Bill

Problem with MSSQL 2005 maintenence plan

Hi,
I am facing a problem with MSSQL 2005 maintenance plan. I created a plan which takes full backup of all the db’s and in the same plan I added a clean up task which is suppose to clean all the files older that 1 day.
To gain compression I converted this plan to lite speed. Now the problem is Backups are running fine but the clean task is not cleaning old files. The job runs fine without fail.
Any body who has faced similar problem please let me know if have the solution ?
Thanks in advance.
Kishan

Hi in this case my date format used in backup file getutcdate() format but
to delete files i am using this script
Declare @sql varchar(250),@retention tinyint
set @retention=0
set @sql='Exec master.dbo.xp_cmdshell ''Del E:\SQL2005\Backup\*' + convert(varchar(15),getdate()-@retention,120) + '*.bak'''
Exec (@sql)
i also tried with getutcdate()
but it gives the following error.
Could Not Find \\E:\SQL2005\Backup\*2008-04-03*.bak
why i donot understand.
can any one give heads up.

Oracle 9i & 10g replicated to MSSQL 2005 Enterprise: Problem !

Hi,
I have been doing some oracle 9i and 10g Replication to MSSQL 2005 Enterprise Database using the SQL 2005 Server Enterprise replication tool. This is working great, however, we recentrly had some problems on the Oracle side getting errors on new connection for both 9i and 10g servers. Only restarting the server has solved the problem so far....
The complete procedure to to this setup is available on Microsoft Technet:
http://www.microsoft.com/technet/prodtechnol/sql/2005/technologies/repl_quickstart_for_oracle.mspx
If anyone could help me regarding the problem on new connections problem I would appreciate
Here are the errors we are getting:
10g Agent connection Error on the Database 10g:
Timestamp=Jul 4, 2008 2:29:03 PM EDT
Severity=Critical
Message=Failed to connect to database instance: ORA-12518: TNS:listener could not hand off client connection (DBD ERROR: OCIServerAttach).
10g Agent connection Error on the Database 9i:
Timestamp=Jul 10, 2008 10:51:16 AM EDT
Severity=Critical
Message=Failed to connect to database instance: ORA-04031: unable to allocate %s bytes of shared memory ("%s","%s","%s","%s") (DBD ERROR: OCISessionBegin).
Notification Rule Name=Send Email For Database Event
Notification Rule Owner=SYSMAN
Notification Count=1
The clients applications are having similar errors when trying to connect. This seems to be happening after replication has been running for a while (1 -2 weeks) on the SQL server 2005 side...
We are using Snapshot Replication for the 10g database (every 20 minutes)
and transactional replication on the 9i database...
We are replicating 28 tables from the 10g database (500Mb Via Snapshot Replication)
And 171 Tables for the 9i databases (Near 3Gb Via Transactional Replication)
Thanks for the help !

Here is an error from the 9i database Client: (this seems to be correct %s values)
ORA-04031: Unable to allocate 20236 bytes of shared memory("shared pool", "unknown object", "sga heap(1,0)", "session param values");
Here is the 9i database Init.ora:
# Copyright (c) 1991, 2001, 2002 by Oracle Corporation
# Cache and I/O
db_block_size=8192
db_cache_size=25165824
db_file_multiblock_read_count=16
# Cursors and Library Cache
open_cursors=300
# Database Identification
db_domain=Something.com
db_name=Something
# Diagnostics and Statistics
background_dump_dest=C:\oracle\admin\Something\bdump
core_dump_dest=C:\oracle\admin\Something\cdump
timed_statistics=TRUE
user_dump_dest=C:\oracle\admin\Something\udump
# File Configuration
control_files=("D:\oracle\oradata\Something\CONTROL01.CTL", "D:\oracle\oradata\Something\CONTROL02.CTL", "D:\oracle\oradata\Something\CONTROL03.CTL")
# Instance Identification
instance_name=Something
# Job Queues
job_queue_processes=10
# MTS
dispatchers="(PROTOCOL=TCP) (SERVICE=SomethingXDB)"
# Miscellaneous
aq_tm_processes=1
compatible=9.2.0.0.0
# Optimizer
hash_join_enabled=TRUE
query_rewrite_enabled=FALSE
star_transformation_enabled=FALSE
# Pools
java_pool_size=33554432
large_pool_size=8388608
shared_pool_size=50331648
# Processes and Sessions
processes=150
# Redo Log and Recovery
fast_start_mttr_target=300
# Security and Auditing
remote_login_passwordfile=EXCLUSIVE
# Sort, Hash Joins, Bitmap Indexes
pga_aggregate_target=25165824
sort_area_size=524288
# System Managed Undo and Rollback Segments
undo_management=AUTO
undo_retention=10800
undo_tablespace=UNDOTBS1
Here is the Database 10g init.ora:
SomeDB.__db_cache_size=1216348160
SomeDB.__java_pool_size=8388608
SomeDB.__large_pool_size=8388608
SomeDB.__shared_pool_size=343932928
SomeDB.__streams_pool_size=0
*.audit_file_dest='D:\oracle\product\10.2.0\admin\SomeDB\adump'
*.background_dump_dest='D:\oracle\product\10.2.0\admin\SomeDB\bdump'
*.compatible='10.2.0.3.0'
*.control_files='D:\oracle\product\10.2.0\oradata\SomeDB\control01.ctl','D:\oracle\product\10.2.0\oradata\SomeDB\control02.ctl','D:\oracle\product\10.2.0\oradata\SomeDB\control03.ctl'
*.core_dump_dest='D:\oracle\product\10.2.0\admin\SomeDB\cdump'
*.db_block_size=8192
*.db_domain=''
*.db_file_multiblock_read_count=16
*.db_name='SomeDB
*.job_queue_processes=10
*.log_archive_dest='D:\Backup\SomeDB\Archives'
*.log_archive_start='true'
*.open_cursors=300
*.pga_aggregate_target=525336576
*.processes=150
*.remote_login_passwordfile='EXCLUSIVE'
*.sga_target=1578106880
*.undo_management='AUTO'
*.undo_tablespace='RBS'
*.user_dump_dest='D:\oracle\product\10.2.0\admin\SomeDB\udump'
On the 10g database we get the error: ORA-12518: TNS:listener could not hand off client connection (DBD ERROR: OCIServerAttach).
The application for the Database 10g Is web based and uses Tomcat, I seems to get similar errors in the tomcat log:
java.sql.SQLException: ORA-04030: out of process memory when trying to allocate 1046552 bytes

Terminology differences between MSSQL 2005/2008 and Oracle 11g

I'm looking for some articles/books/webinars/blogs which discuss the terminology differences between MSSQL 2005/2008 and Oracle 11g in terms of database concepts. I have found this article http://www.sqlservercentral.com/articles/SQL+Server/67007 so far.
Thanks.

Thanks sb92075. Those returned results are almost all related to compare the features/functionalities between MSSQL and Oracle not to distinguish the terminology differences between them.

ODI 10.1.3.4.0 - Topology Manager Connection Error using SQL 2005 SP3

Hello All,
I am using the ODI repository in SQL 2005 SP3. I could create my master repository using the following parameters:
driver: com.microsoft.sqlserver.jdbc.SQLServerDriver
URL:jdbc:microsoft:sqlserver://server_name:1433;SelectMethod=direct;DataBaseName=ODI
I needed to copy to the drivers directory all files of SQL 2000 (msutil.jar, msbase.jar,mssqlserver.jar) and SQL 2005 (sqljdbc.jar). I am using the JRE 1.4.2 and JDBC 2005 1.2 (http://msdn.microsoft.com/en-us/library/ms378422(SQL.90).aspx)
But when I try to connect in Topology Manager to create the work repository appears the following error:
using this driver string: com.microsoft.jdbc.sqlserver.SQLServerDriver
java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC] Can't start a cloned connection while in manual transaction mode.
using this driver string: com.microsoft.sqlserver.jdbc.SQLServerDriver
java.sql.SQLException: No suitable driver
Does Somebody know what is happening?
Regards,
Wallace Galvao
Sao Paulo - Brazil

Hi,
If you plan on using the SQL Server 2005 drivers then you only need the 1.2 sqljdbc.jar file in the drivers directory.
The connection details for SQL Server 2005 should be like the following.
com.microsoft.sqlserver.jdbc.SQLServerDriver
jdbc:sqlserver://<sqls machine>:1433;databaseName=<db name>;integratedSecurity=false
I would try just with just the correct driver in place, remove the others, restart any ODI components and then make sure the connection information is correct like above.
Cheers
John
http://john-goodwin.blogspot.com/

BI JDBC Connection For MSSQL 2005

Hi All,
I am trying to establish an BI JDBC Connection with MSSQL 2005 Server. I follow the steps exactly mentioned in the guide but i was not successfull. I doubt the problem could be with the adapters and again downloaded a JAR file for MSSQL 2005 from microsoft website and proceeded with steps. But no luck this time also.
How do i make a successfull connection. Below is the result of a test page
==================================================
Details:
com.sap.ip.bi.sdk.exception.BIConnectionFailedException: Cannot open the connection at com.sap.ip.bi.sdk.dac.connector.jdbc.JdbcConnectionFactory.getConnectionEx(JdbcConnectionFactory.java:238) at com.sap.ip.bi.sdk.trialarea.connector.servlet.model.JDBCModel.getConnection(JDBCModel.java:797) at com.sap.ip.bi.sdk.trialarea.connector.servlet.model.JDBCModel.getTables(JDBCModel.java:132) at com.sap.ip.bi.sdk.trialarea.connector.servlet.controller.Control2.doPost(Control2.java:23) at javax.servlet.http.HttpServlet.service(HttpServlet.java:760) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365) at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944) at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266) at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95) at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:160) at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33) at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170) Caused by: com.sap.ip.bi.sdk.exception.BIResourceException: Cannot open the connection at com.sap.ip.bi.sdk.dac.connector.jdbc.JdbcManagedConnection.(JdbcManagedConnection.java:123) at com.sap.ip.bi.sdk.dac.connector.jdbc.JdbcManagedConnectionFactory.createManagedConnection(JdbcManagedConnectionFactory.java:119) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(ConnectionHashSet.java:320) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:189) at com.sap.ip.bi.sdk.dac.connector.jdbc.JdbcConnectionFactory.getConnectionEx(JdbcConnectionFactory.java:233) ... 19 more Caused by: com.sap.ip.bi.sdk.exception.BIResourceException: Cannot connect to JDBC data source at com.sap.ip.bi.sdk.dac.connector.jdbc.impl.Connection.connectDB(Connection.java:394) at com.sap.ip.bi.sdk.dac.connector.jdbc.impl.Connection.connect(Connection.java:106) at com.sap.ip.bi.sdk.dac.connector.jdbc.JdbcManagedConnection.(JdbcManagedConnection.java:118) ... 23 more Caused by: java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]End of stream was detected on a read. at com.microsoft.jdbc.base.BaseExceptions.createException(Unknown Source) at com.microsoft.jdbc.base.BaseExceptions.getException(Unknown Source) at com.microsoft.jdbc.sqlserver.tds.TDSRequest.processReply(Unknown Source) at com.microsoft.jdbc.sqlserver.SQLServerImplConnection.open(Unknown Source) at com.microsoft.jdbc.base.BaseConnection.getNewImplConnection(Unknown Source) at com.microsoft.jdbc.base.BaseConnection.open(Unknown Source) at com.microsoft.jdbc.base.BaseDriver.connect(Unknown Source) at java.sql.DriverManager.getConnection(DriverManager.java:512) at java.sql.DriverManager.getConnection(DriverManager.java:140) at com.sap.ip.bi.sdk.dac.connector.jdbc.impl.Connection.connectDB(Connection.java:376) ... 25 more
====================================================
regards,
Anand

Hi Anand,
did you check the WIKI:
<a href="https://wiki.sdn.sap.com/wiki/display/VC/JDBCConnectionSetup">https://wiki.sdn.sap.com/wiki/display/VC/JDBCConnectionSetup</a>
Best Regards,
Marcel

MSSQL 2005 SP3 installation

Similar Messages

Maybe you are looking for