Identify installed database is a DEMO or SYSTEM database

Is there any table tells the installed database is a DEMO or SYSTEM database in Peoplesoft? (or) is there any way to identify the same?
Thanks

There is nothing by default, unless the admin who created the database filled the proper columns :
SQL> select systemtype,shortname,longname from psoptions;
SYSTEMTYP SHORTNAME
LONGNAME
DMO HDMO91
Demo database 9.1Or check if you have employees data (DEMO) or not (SYS).
Nicolas.

Similar Messages

MSSQL 2005 user database now shows up in system database folder

While attempting to set up sql replication in MSSQL 2005 one of my user databases is now in the systems database folder. I need to move it back to the user databases folder. Any help would be greatly appreciated.

I'm still at the point where if I run
sp_detach_db 'dbname'
I get
Msg 3724, Level 16, State 1, Line 1
Cannot drop the database 'dbname' because it is being used for replication.
If I right click on the replication folder I have no disbributor properties
Somehow I need to remvoe the replication flag from the db that I have accidentally gotten it stuck on.
Any ideas?
Hello dsams,
Are you a member of "sysadmin" fixed server role ? If not you will not be able to configure replication.
Once you are a member of "sysadmin" then you can try the below sql or go to replication and right click on it, you will get "Disable publishing & distribution".
use master
go
alter database distribution set offline;
drop database distribution;
Regards, RSingh

Error -1074384569; NI-XNET: (Hex 0xBFF63147) The database information on the real-time system has been created with an older NI-XNET version. This version is no longer supported. To correct this error, re-deploy your database to the real-time system.

Hello
I have a VeriStand-Project (VSP) created with my Laptop-Host (LTH) which works with my PXI, while
deploying it from my LTH. Then I have installed the whole NI enviroment for PXI and VeriStand use on a
industrial PC (iPC). I have tried to deploy my VSP from the iPC to the PXI but the following error
message arose on my iPC:
The VeriStand Gateway encountered an error while deploying the System Definition file.
Details: Error -1074384569 occurred at Project Window.lvlibroject Window.vi >> Project
Window.lvlib:Command Loop.vi >> NI_VS Workspace ExecutionAPI.lvlib:NI VeriStand - Connect to System.vi
Possible reason(s):
NI-XNET: (Hex 0xBFF63147) The database information on the real-time system has been created with an
older NI-XNET version. This version is no longer supported. To correct this error, re-deploy your
database to the real-time system. ========================= NI VeriStand: NI VeriStand
Engine.lvlib:VeriStand Engine Wrapper (RT).vi >> NI VeriStand Engine.lvlib:VeriStand Engine.vi >> NI
VeriStand Engine.lvlib:VeriStand Engine State Machine.vi >> NI VeriStand Engine.lvlib:Initialize
Inline Custom Devices.vi >> Custom Devices Storage.lvlib:Initialize Device (HW Interface).vi
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * • Unloading System
Definition file... • Connection with target Controller has been lost.
The software versions of the NI products (MAX/My System/Software) between my LTH and the iPC are
almost the same. The only differences are:
1. LabView Run-Time 2009 SP1 (64-bit); is installed on LTH but missing on iPC. The iPC has a 32-bit system.
2. LabView Run-Time 2012 f3; is installed on LTH but missing on iPC.
3. NI-DAQmx ADE Support 9.3.5; something strage on the LTH, because normally I am using NI-DAQmx 9.5.5 and all other DAQmx products on my LTH are 9.5.5. That means NI-DAQmx Device Driver 9.5.5 and NI-DAQmx Configuration 9.5.5.. On the iPC side all three products are 9.5.5.. That means NI-DAQmx ADE Support 9.5.5, NI-DAQmx Device Driver 9.5.5 and NI-DAQmx Configuration 9.5.5..
4. Traditional NI-DAQ 7.4.4; The iPC has this SW installed. On the LTH this SW is missing.
In order to fix this problem I have formatted my PXI and I have installed the following SW from the iPC:
1. LabVIEW Real-Time 11.0.1
2. NI-488.2 RT 3.0.0
3. NI_CAN 2.7.3
Unfortunately the above stated problem still arose.
What can I do to fix this problem?
I found a hint on http://www.labviewforum.de/Thread-XNET-CAN-die-ersten-Gehversuche.
There it is written to deploy the dbc file againt.
If this is a good hint, so how do I deploy a dbc file?
I would feel very pleased if somebody could help me! :-)
Best regards
Lukas Nowak

Hi Lukas,
I think the problem is caused by differenet drivers for the CAN communication.
NI provides two driver for CAN: NI-CAN and NI-XNET.
NI-CAN is the outdated driver which is not longer used by new hardware. NI replaced the NI-CAN driver with NI-XNET some years ago, which supports CAN, LIN and the FLEXRAY communication protocol.
You wrote:
In order to fix this problem I have formatted my PXI and I have installed the following SW from the iPC:
3. NI_CAN 2.7.3
NI CAN is the outdated driver. I think that you should try to install NI-XNET instead of NI-CAN on your PXI-System, to get rid of the error message.
Regards, stephan

Error while performing silent install of 10.1.0.2 infrastructure database

Hello,
I'm trying to create a silent install for a 10.1.0.2 database. I created the response file using the -record option for the installer. I then modified the response file according to the instructions in the app server installation documentation. When I run setup with the response file I get the follow error...
Starting Oracle Universal Installer...
Checking installer requirements...
Checking operating system version: must be 5.0, 5.1 or 5.2 . Actual 5.0
Passed
Checking swap space: must be greater than 1535 MB . Actual 4092MB Passed
Checking for SERVICE_PACK: must be 3 . Actual Service Pack 4 Passed
Checking Temp space: must be greater than 150 MB . Actual 60731 MB Passed
All installer requirements met.
Preparing to launch Oracle Universal Installer from C:\DOCUME~1\cdwright\LOCALS
~1\Temp\OraInstall2008-04-30_06-38-27PM. Please wait ... Oracle Universal Instal
ler, Version 10.1.0.4.0 Production
Copyright (C) 1999, 2005, Oracle. All rights reserved.
Loading Product Information
...............................................................100% Done.
Analyzing dependencies
.........Error:*** Alert: An error occurred attempting to find the ASControl ser
vice executable in this Oracle Home. Please verify that the file C:\oracle\infra
\bin\nmesrvc.exe exists in this home or that this Oracle Home is valid. ***
Why is the installer looking for ASControl? This should be a fresh install. Any help I can get would be much appreciated.
Cliff Wright

Hi Cliff
What is happening when you try to do the installation with OUI not in silent mode`?
Does it works?
Could it be possible to have the errors from the installation log please?
Thanks

I can not create an Installer, After install the Vision Builder Demo and then uninstall it. I can not create a Labview installer anymore, it asks me for a Vision Builder Installer, even if My Labview program does not have nothing to do with it...

I can not create an Installer on LabView, After install the Vision Builder Demo and then uninstall it. I can not create a Labview installer anymore, it asks me for a Vision Builder Installer, even if My Labview program does not have nothing to do with it...
Solved!
Go to Solution.

Hi Shada this can happen if you are including additional installers to your installer for example DAQmx. When you are doing this the installer has to include other files like MAX (Measuremente and Automation Explorer). Probably when you installed Vision Builder it updated MAX, so when your installer is trying to Include MAX, its asking for the source where it was installed in your computer in this case Vision Builder.
Here you can cache the information so its not asked again, or you can download a newer version fo DAQmx, so it will update MAX and change de dependecy.
You can find more details about this issue in this KB:
KnowledgeBase 3S88PJMY: Why Do I Get A "Missing Distribution" Error When Trying to Build an Installe...
And for keeping a copy here is more info:
How Do I Stop the Missing Distribution Notification Each Time I Build An Installer?
Best Regards
Benjamin C
Senior Systems Engineer // CLA // CLED // CTD

The CMS system database is not available (FWM 02088)

Hi all,
After installation of BOE 3.1 the system fires back the error message on attempt to logon to CMS:
Account Information Not Recognized: The CMS system database is not available. This error cannot be rectified by the end user. Report this error to your system administrator or database administrator. (FWM 02088)
Any inputs? I've tried with new SIA as well as fresh installation but the issue persists.
Regards.

were you able to see any DB error messages in event log ?
can you connect to your DB from the server itself ? (could be FW issue)
What do you see under the CCM ? Do the SIA is in green state ?
For me it is probably one of 2 things : FW issue (but install will have failed) or DB issue
Sam.
Edited by: sjolly on Sep 17, 2009 9:46 AM

Many invalid objects found after new install the R12 vision demo (12.1.1)

In AIX Server,
I found many invalid objects after new install the R12 vision demo (12.1.1) with DB v11.1.0.7, can I drop the following invalid objects then upgrade to R12.1.3 ?
OWNER OBJECT_NAME OBJECT_TYPE STATUS
APPS XLA_00707_AAD_C_000026_PKG PACKAGE BODY INVALID
APPS XLA_00200_AAD_C_000017_PKG PACKAGE BODY INVALID
APPS XLA_00200_AAD_C_000016_PKG PACKAGE BODY INVALID
APPS XLA_00200_AAD_S_000032_PKG PACKAGE BODY INVALID
APPS XLA_00200_AAD_S_000034_PKG PACKAGE BODY INVALID
APPS XLA_00200_AAD_S_000039_PKG PACKAGE BODY INVALID
APPS XLA_00200_AAD_S_000041_PKG PACKAGE BODY INVALID
APPS XLA_00200_AAD_C_000020_PKG PACKAGE BODY INVALID
RE RE_PROFILER PACKAGE BODY INVALID
APPS XLA_00200_AAD_C_000018_PKG PACKAGE BODY INVALID
APPS XLA_00200_AAD_C_000021_PKG PACKAGE BODY INVALID
APPS XLA_00555_AAD_S_000014_PKG PACKAGE BODY INVALID
APPS XLA_00555_AAD_C_000015_PKG PACKAGE BODY INVALID
APPS XLA_00200_AAD_C_000022_PKG PACKAGE BODY INVALID
APPS XLA_00140_AAD_S_000036_PKG PACKAGE BODY INVALID
APPS FSAH_DUPLICATE_PKG PACKAGE BODY INVALID
APPS XLA_00707_AAD_C_000044_PKG PACKAGE BODY INVALID
APPS MSD_DEM_OBI_DEMANTRA_MV MATERIALIZED VIEW INVALID
18 rows selected.
SQL> alter package XLA_00707_AAD_C_000026_PKG compile body;
Warning: Package Body altered with compilation errors.
SQL> show error
Errors for PACKAGE BODY XLA_00707_AAD_C_000026_PKG:
LINE/COL ERROR
1/49 PLS-00103: Encountered the symbol "end-of-file" when expecting one of the following:
is as compress compiled wrapped
The symbol "compress" was substituted for "end-of-file" to continue.
SQL> alter package RE.RE_PROFILER compile body;
Warning: Package Body altered with compilation errors.
SQL> show error
Errors for PACKAGE BODY RE.RE_PROFILER:
LINE/COL ERROR
1180/13 PL/SQL: SQL Statement ignored
1180/13 PLS-00435: DML statement without BULK In-BIND cannot be used inside FORALL
1181/32 PLS-00440: FORALL bulk IN-bind variables cannot be used here
1926/9 PL/SQL: SQL Statement ignored
1926/9 PLS-00435: DML statement without BULK In-BIND cannot be used inside FORALL
SQL> alter package FSAH_DUPLICATE_PKG compile body;
Warning: Package Body altered with compilation errors.
SQL> show error
Errors for PACKAGE BODY FSAH_DUPLICATE_PKG:
LINE/COL ERROR
7/12 PLS-00341: declaration of cursor 'C1' is incomplete or malformed
8/7 PL/SQL: SQL Statement ignored
9/14 PL/SQL: ORA-00942: table or view does not exist
12/17 PL/SQL: Item ignored
16/7 PL/SQL: SQL Statement ignored
16/71 PL/SQL: ORA-00942: table or view does not exist
22/13 PL/SQL: SQL Statement ignored
22/27 PLS-00320: the declaration of the type of this expression is incomplete or malformed
Edited by: SamCH on 2013年2月4日下午11:19

Hi Hussein,
Thanks for your reply again, the compile error as below
e.g.
show error
SQL> ALTER PACKAGE APPS.XLA_00707_AAD_C_000026_PKG COMPILE BODY;
Warning: Package Body altered with compilation errors.
SQL> show error
Errors for PACKAGE BODY APPS.XLA_00707_AAD_C_000026_PKG:
LINE/COL ERROR
1/49 PLS-00103: Encountered the symbol "end-of-file" when expecting one of the following:
is as compress compiled wrapped
The symbol "compress" was substituted for "end-of-file" to continue.
SQL> ALTER PACKAGE APPS.XLA_00200_AAD_C_000017_PKG COMPILE BODY;
Warning: Package Body altered with compilation errors.
SQL> show error
Errors for PACKAGE BODY APPS.XLA_00200_AAD_C_000017_PKG:
LINE/COL ERROR
131072/2 PLS-00103: Encountered the symbol "end-of-file" when expecting
one of the following:
( begin case declare end exit for goto if loop mod null
pragma raise return select update while with <an identifier>
<a double-quoted delimited-identifier> <a bind variable> <<
continue close current delete fetch lock insert open rollback
savepoint set sql execute commit forall merge pipe purge
SQL> ALTER PACKAGE APPS.XLA_00200_AAD_S_000032_PKG COMPILE BODY;
Warning: Package Body altered with compilation errors.
SQL> show error
Errors for PACKAGE BODY APPS.XLA_00200_AAD_S_000032_PKG:
LINE/COL ERROR
131072/7 PLS-00103: Encountered the symbol "end-of-file" when expecting
2 one of the following:
. ( ) , * % & = - + < / > at in is mod remainder not rem
<an exponent (**)> <> or != or ~= >= <= <> and or like like2
like4 likec between || multiset member submultiset
SQL> ALTER PACKAGE RE.RE_PROFILER COMPILE BODY;
Warning: Package Body altered with compilation errors.
SQL> show error
Errors for PACKAGE BODY RE.RE_PROFILER:
LINE/COL ERROR
1180/13 PL/SQL: SQL Statement ignored
1180/13 PLS-00435: DML statement without BULK In-BIND cannot be used inside FORALL
1181/32 PLS-00440: FORALL bulk IN-bind variables cannot be used here
1926/9 PL/SQL: SQL Statement ignored
1926/9 PLS-00435: DML statement without BULK In-BIND cannot be used inside FORALL
SQL> ALTER PACKAGE APPS.XLA_00555_AAD_S_000014_PKG COMPILE BODY;
Warning: Package Body altered with compilation errors.
SQL> show error
Errors for PACKAGE BODY APPS.XLA_00555_AAD_S_000014_PKG:
LINE/COL ERROR
131072/5 PLS-00103: Encountered the symbol "end-of-file" when expecting
7 one of the following:
begin function pragma procedure subtype type <an identifier>
<a double-quoted delimited-identifier> current cursor delete exists prior
SQL> ALTER PACKAGE APPS.FSAH_DUPLICATE_PKG COMPILE BODY;
Warning: Package Body altered with compilation errors.
SQL> show error
Errors for PACKAGE BODY APPS.FSAH_DUPLICATE_PKG:
LINE/COL ERROR
7/12 PLS-00341: declaration of cursor 'C1' is incomplete or malformed
8/7 PL/SQL: SQL Statement ignored
9/14 PL/SQL: ORA-00942: table or view does not exist
12/17 PL/SQL: Item ignored
16/7 PL/SQL: SQL Statement ignored
16/71 PL/SQL: ORA-00942: table or view does not exist
22/13 PL/SQL: SQL Statement ignored
22/27 PLS-00320: the declaration of the type of this expression is incomplete or malformed
SQL> ALTER PACKAGE APPS.XLA_00707_AAD_C_000044_PKG COMPILE BODY;
Warning: Package Body altered with compilation errors.
SQL> show error
Errors for PACKAGE BODY APPS.XLA_00707_AAD_C_000044_PKG:
LINE/COL ERROR
201713/1 PL/SQL: SQL Statement ignored
201826/1 PL/SQL: ORA-00904: "CST_XLA_INV_REF_V"."TRANSACTION_SOURCE_ID":
30 invalid identifier
202147/1 PL/SQL: SQL Statement ignored
202191/1 PL/SQL: ORA-00904: "CST_XLA_INV_REF_V"."TRANSACTION_SOURCE_ID":
30 invalid identifier
202973/5 PL/SQL: Statement ignored
202973/2 PLS-00364: loop index variable 'HEADER_RECORD' use is invalid
7
SQL> ALTER PACKAGE APPS.POS_AP_SUPPLIER_BO_PKG COMPILE BODY;
Warning: Package Body altered with compilation errors.
SQL> show error
Errors for PACKAGE BODY APPS.POS_AP_SUPPLIER_BO_PKG:
LINE/COL ERROR
0/0 PL/SQL: Compilation unit analysis terminated
1/14 PLS-00304: cannot compile body of 'POS_AP_SUPPLIER_BO_PKG' without its specification
1/14 PLS-00905: object APPS.POS_AP_SUPPLIER_BO_PKG is invalid
SQL> ALTER PACKAGE APPS.POS_AP_SUPPLIER_BO_PKG COMPILE ;
Warning: Package altered with compilation errors.
SQL> show error
Errors for PACKAGE APPS.POS_AP_SUPPLIER_BO_PKG:
LINE/COL ERROR
3/3 PL/SQL: Declaration ignored
7/32 PLS-00201: identifier 'POS_AP_SUPPLIER_BO' must be declared
28/3 PL/SQL: Declaration ignored
35/40 PLS-00201: identifier 'POS_AP_SUPPLIER_BO' must be declared
SQL> ALTER PACKAGE APPS.POS_BANK_ACCOUNT_BO_PKG COMPILE BODY;
Warning: Package Body altered with compilation errors.
SQL> show error
Errors for PACKAGE BODY APPS.POS_BANK_ACCOUNT_BO_PKG:
LINE/COL ERROR
0/0 PL/SQL: Compilation unit analysis terminated
1/14 PLS-00304: cannot compile body of 'POS_BANK_ACCOUNT_BO_PKG' without its specification
1/14 PLS-00905: object APPS.POS_BANK_ACCOUNT_BO_PKG is invalid
SQL> ALTER PACKAGE APPS.POS_BANK_ACCOUNT_BO_PKG COMPILE ;
Warning: Package altered with compilation errors.
SQL> show error
Errors for PACKAGE APPS.POS_BANK_ACCOUNT_BO_PKG:
LINE/COL ERROR
4/6 PL/SQL: Declaration ignored
9/80 PLS-00201: identifier 'POS_BANK_ACCOUNT_BO_TBL' must be declared
13/5 PL/SQL: Declaration ignored
19/69 PLS-00201: identifier 'POS_BANK_ACCOUNT_BO_TBL' must be declared

No size history for SQL Database in dbacockpit for new system

Hello,
we have installed a new ERP 6.0 System on Windows with SQL Server 2005 (3 month ago)
Now we haven´t any data in datbase size historie in the dbacockpit.
The message is: No size history. Check the DB Collector status.
We checked already the state of Collector. It is running every 20 minutes and collect data for performance. But not for the growth of the database.
We also deleted the job at the SQL Agent and planned it new with the report MSSPROCS.
Does anyone have an idea whats the problem?
Best regards
Petra Wöritz

Hello all together,
we are facing the same problem until now.
I checked all the points you suggested:
- the performance collector job runs in client 000
- time zone is set to CET
- the SAPOSCOL is running
- no errors by executing the SQL statement EXECUTE sap_dbcoll
- no errors in SQL Job SAP_sid_SID_MSSQL_COLLECTOR
We don't have any data in size history.
But we found a error message in dev_w0:
C dbdsmss: DBSL26 SQL3621C Violation of PRIMARY KEY constraint 'PK__#perfinfo_________0C5BC11B'. Cannot insert duplicate key in object 'dbo.#perfinfo'.The statement has been terminated
It occurs, when we try get the data of history in db02 (or dbacockpit).
The note 1171828 doen't fit.
We have already SAP_BASIS 701 0007
We've got a system with SAP_BASIS 702 0006
There the error is displayed in dbacockpit directly:
SQL-Fehler 2627: [Microsoft][SQL Native Client][SQL Server]Violatio n of PRIMARY KEY constraint 'PK__#perfinfo________ _5A303401'. Cannot insert duplicate key in object
Any ideas?
Best regards
Petra

Cannot Install Sql Server 2008, Gives The Error "Database Engine Services Failed"

I cannot install Sql Server 2008 R2 on Windows 8. Tried many times but failed because it gives the error "Database
Engine Services Failed". Sql files cannot be corrupted because i can install the same setup on Windows 7 and i can connect to databases.
I tried all the things below;
* I'm uninstalling everything related with Sql Server from Control Panel/Programs And Features.
* I'm deleting all the keys related with Sql Server from Regedit.
* Later i'm restarting windows, and trying to install again. But during the install it gives the error "Database
Engine Services Failed", install is finishing but when i opened the Management Studio i cannot connect to Database Engine with Sa naturally.
* My firewall is already closed. And i have not any antivirus software.
* I gave the permission for port 1433 on firewall.
Please help me. Why i always take "Database Engine Services Failed" error? I will get crazy cause of that for many days.

Here's the ERRORLOG file which i found under the folder;
Microsoft SQL Server/MSSQL10_50.MSSQLSERVER/MSSQL/Log.
2014-09-27 03:39:40.15 Server Microsoft SQL Server 2008 R2 (RTM) - 10.50.1600.1 (X64)
Apr 2 2010 15:48:46
Copyright (c) Microsoft Corporation
Developer Edition (64-bit) on Windows NT 6.2 <X64> (Build 9200: )
2014-09-27 03:39:40.15 Server (c) Microsoft Corporation.
2014-09-27 03:39:40.15 Server All rights reserved.
2014-09-27 03:39:40.15 Server Server process ID is 5768.
2014-09-27 03:39:40.15 Server System Manufacturer: 'SAMSUNG ELECTRONICS CO., LTD.', System Model: '350V5C/350V5X/350V4C/350V4X/351V5C/351V5X/351V4C/351V4X/3540VC/3540VX/3440VC/3440VX'.
2014-09-27 03:39:40.15 Server Authentication mode is MIXED.
2014-09-27 03:39:40.15 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG'.
2014-09-27 03:39:40.15 Server Registry startup parameters:
-d C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\master.mdf
-e C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG
-l C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\mastlog.ldf
2014-09-27 03:39:40.15 Server Command Line Startup Parameters:
-m SqlSetup
-f
-Q
-q Turkish_CI_AS
-T 4022
-T 4010
-T 3659
-T 3610
2014-09-27 03:39:40.18 Server Warning: The server instance was started using minimal configuration startup option (-f). Starting an instance of SQL Server with minimal configuration places the server in single-user mode automatically. After
the server has been started with minimal configuration, you should change the appropriate server option value or values, stop, and then restart the server.
2014-09-27 03:39:40.18 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2014-09-27 03:39:40.18 Server Detected 4 CPUs. This is an informational message; no user action is required.
2014-09-27 03:39:40.31 Server Perfmon counters for resource governor pools and groups failed to initialize and are disabled.
2014-09-27 03:39:40.32 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
2014-09-27 03:39:40.43 Server Node configuration: node 0: CPU mask: 0x000000000000000f:0 Active CPU mask: 0x000000000000000f:0. This message provides a description of the NUMA configuration for this computer. This is an informational message
only. No user action is required.
2014-09-27 03:39:40.45 Server Support for distributed transactions was not enabled for this instance of the Database Engine because it was started using the minimal configuration option. This is an informational message only. No user action
is required.
2014-09-27 03:39:40.45 spid7s Warning ******************
2014-09-27 03:39:40.45 spid7s SQL Server started in single-user mode. This an informational message only. No user action is required.
2014-09-27 03:39:40.46 spid7s Starting up database 'master'.
2014-09-27 03:39:40.52 spid7s Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2014-09-27 03:39:40.58 spid7s SQL Server was started using the -f flag. SQL Server Audit is disabled. This is an informational message. No user action is required.
2014-09-27 03:39:40.59 spid7s FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
2014-09-27 03:39:40.59 spid7s Server started with '-f' option. Auditing will not be started. This is an informational message only; no user action is required.
2014-09-27 03:39:40.59 spid7s Starting up database 'mssqlsystemresource'.
2014-09-27 03:39:40.61 spid7s The resource database build version is 10.50.1600. This is an informational message only. No user action is required.
2014-09-27 03:39:40.94 spid7s Password policy update was successful.
2014-09-27 03:39:40.94 spid8s Starting up database 'model'.
2014-09-27 03:39:40.95 spid7s Server name is 'CAGATAY'. This is an informational message only. No user action is required.
2014-09-27 03:39:41.21 spid8s Clearing tempdb database.
2014-09-27 03:39:41.21 spid10s A new instance of the full-text filter daemon host process has been successfully started.
2014-09-27 03:39:41.24 Server A self-generated certificate was successfully loaded for encryption.
2014-09-27 03:39:41.24 Server Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
2014-09-27 03:39:41.24 Server Dedicated administrator connection support was not started because it is disabled on this edition of SQL Server. If you want to use a dedicated administrator connection, restart SQL Server using the trace flag
7806. This is an informational message only. No user action is required.
2014-09-27 03:39:41.28 Server The SQL Server Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service. Error: 0x54b, state: 3. Failure to register an SPN may cause integrated authentication
to fall back to NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies.
2014-09-27 03:39:41.28 Server SQL Server is now ready for client connections. This is an informational message; no user action is required.
2014-09-27 03:39:41.70 spid8s Starting up database 'tempdb'.
2014-09-27 03:39:41.86 spid7s Warning ******************
2014-09-27 03:39:41.86 spid7s Attempting to change default collation to Turkish_CI_AS.
2014-09-27 03:39:41.92 spid7s index restored for master.syspriorities.
2014-09-27 03:39:41.95 spid7s index restored for master.sysbrickfiles.
2014-09-27 03:39:41.96 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:41.96 spid7s index restored for master.sysowners.
2014-09-27 03:39:42.13 spid7s index restored for master.sysdbreg.
2014-09-27 03:39:42.16 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.16 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.16 spid7s index restored for master.sysschobjs.
2014-09-27 03:39:42.17 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.17 spid7s index restored for master.syscolpars.
2014-09-27 03:39:42.17 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.18 spid7s index restored for master.sysxlgns.
2014-09-27 03:39:42.18 spid7s index restored for master.sysxsrvs.
2014-09-27 03:39:42.18 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.18 spid7s index restored for master.sysnsobjs.
2014-09-27 03:39:42.18 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.18 spid7s index restored for master.syscerts.
2014-09-27 03:39:42.19 spid7s index restored for master.sysrmtlgns.
2014-09-27 03:39:42.19 spid7s index restored for master.sysxprops.
2014-09-27 03:39:42.19 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.19 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.31 spid7s index restored for master.sysscalartypes.
2014-09-27 03:39:42.31 spid7s index restored for master.sysidxstats.
2014-09-27 03:39:42.31 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.32 spid7s index restored for master.sysendpts.
2014-09-27 03:39:42.32 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.32 spid7s index restored for master.sysclsobjs.
2014-09-27 03:39:42.32 spid7s index restored for master.sysremsvcbinds.
2014-09-27 03:39:42.32 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.32 spid7s index restored for master.sysrts.
2014-09-27 03:39:42.33 spid7s index restored for master.sysasymkeys.
2014-09-27 03:39:42.33 spid7s index restored for master.syssqlguides.
2014-09-27 03:39:42.44 spid7s index restored for master.syssoftobjrefs.
2014-09-27 03:39:42.47 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.48 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.49 spid7s index restored for master.spt_values.
2014-09-27 03:39:42.49 spid7s index restored for master.MSreplication_options.
2014-09-27 03:39:42.56 spid7s index restored for tempdb.syspriorities.
2014-09-27 03:39:42.56 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.57 spid7s index restored for tempdb.sysowners.
2014-09-27 03:39:42.57 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.57 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.57 spid7s index restored for tempdb.sysschobjs.
2014-09-27 03:39:42.57 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.59 spid7s index restored for tempdb.syscolpars.
2014-09-27 03:39:42.60 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.60 spid7s index restored for tempdb.sysnsobjs.
2014-09-27 03:39:42.60 spid7s index restored for tempdb.syscerts.
2014-09-27 03:39:42.60 spid7s index restored for tempdb.sysxprops.
2014-09-27 03:39:42.60 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.60 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.60 spid7s index restored for tempdb.sysscalartypes.
2014-09-27 03:39:42.61 spid7s index restored for tempdb.sysidxstats.
2014-09-27 03:39:42.61 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.61 spid7s index restored for tempdb.sysclsobjs.
2014-09-27 03:39:42.61 spid7s index restored for tempdb.sysremsvcbinds.
2014-09-27 03:39:42.61 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.61 spid7s index restored for tempdb.sysrts.
2014-09-27 03:39:42.62 spid7s index restored for tempdb.sysasymkeys.
2014-09-27 03:39:42.69 spid7s index restored for tempdb.syssqlguides.
2014-09-27 03:39:42.69 spid7s index restored for tempdb.syssoftobjrefs.
2014-09-27 03:39:42.75 spid7s index restored for model.syspriorities.
2014-09-27 03:39:42.75 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.75 spid7s index restored for model.sysowners.
2014-09-27 03:39:42.76 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.76 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.76 spid7s index restored for model.sysschobjs.
2014-09-27 03:39:42.76 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:43.00 spid7s index restored for model.syscolpars.
2014-09-27 03:39:43.00 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:43.00 spid7s index restored for model.sysnsobjs.
2014-09-27 03:39:43.00 spid7s index restored for model.syscerts.
2014-09-27 03:39:43.00 spid7s index restored for model.sysxprops.
2014-09-27 03:39:43.00 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:43.00 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:43.00 spid7s index restored for model.sysscalartypes.
2014-09-27 03:39:43.00 spid7s index restored for model.sysidxstats.
2014-09-27 03:39:43.01 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:43.01 spid7s index restored for model.sysclsobjs.
2014-09-27 03:39:43.01 spid7s index restored for model.sysremsvcbinds.
2014-09-27 03:39:43.01 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:43.01 spid7s index restored for model.sysrts.
2014-09-27 03:39:43.01 spid7s index restored for model.sysasymkeys.
2014-09-27 03:39:43.01 spid7s index restored for model.syssqlguides.
2014-09-27 03:39:43.01 spid7s index restored for model.syssoftobjrefs.
2014-09-27 03:39:43.02 spid7s Starting up database 'msdb'.
2014-09-27 03:39:43.82 spid7s index restored for msdb.syspriorities.
2014-09-27 03:39:43.85 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:43.93 spid7s index restored for msdb.sysowners.
2014-09-27 03:39:43.99 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.00 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.09 spid7s index restored for msdb.sysschobjs.
2014-09-27 03:39:44.12 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.20 spid7s index restored for msdb.syscolpars.
2014-09-27 03:39:44.20 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.20 spid7s index restored for msdb.sysnsobjs.
2014-09-27 03:39:44.20 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.25 spid7s index restored for msdb.syscerts.
2014-09-27 03:39:44.25 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.26 spid7s index restored for msdb.sysxprops.
2014-09-27 03:39:44.26 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.26 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.27 spid7s index restored for msdb.sysscalartypes.
2014-09-27 03:39:44.37 spid7s index restored for msdb.sysidxstats.
2014-09-27 03:39:44.41 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.42 spid7s index restored for msdb.sysclsobjs.
2014-09-27 03:39:44.42 spid7s index restored for msdb.sysremsvcbinds.
2014-09-27 03:39:44.42 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.42 spid7s index restored for msdb.sysrts.
2014-09-27 03:39:44.54 spid7s index restored for msdb.sysasymkeys.
2014-09-27 03:39:44.54 spid7s index restored for msdb.syssqlguides.
2014-09-27 03:39:44.59 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.74 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.85 spid7s index restored for msdb.syssoftobjrefs.
2014-09-27 03:39:44.89 spid7s index restored for msdb.syspolicy_policies_internal.
2014-09-27 03:39:44.90 spid7s index restored for msdb.sysproxies.
2014-09-27 03:39:44.90 spid7s index restored for msdb.syscollector_execution_stats_internal.
2014-09-27 03:39:44.90 spid7s index restored for msdb.syssubsystems.
2014-09-27 03:39:44.91 spid7s index restored for msdb.log_shipping_primary_secondaries.
2014-09-27 03:39:44.91 spid7s index restored for msdb.sysdownloadlist.
2014-09-27 03:39:44.91 spid7s index restored for msdb.log_shipping_monitor_primary.
2014-09-27 03:39:44.92 spid7s index restored for msdb.sysoriginatingservers.
2014-09-27 03:39:44.93 spid7s index restored for msdb.log_shipping_monitor_history_detail.
2014-09-27 03:39:44.95 spid7s index restored for msdb.log_shipping_monitor_error_detail.
2014-09-27 03:39:44.95 spid7s index restored for msdb.log_shipping_secondary.
2014-09-27 03:39:44.97 spid7s index restored for msdb.log_shipping_secondary_databases.
2014-09-27 03:39:45.10 spid7s index restored for msdb.log_shipping_monitor_secondary.
2014-09-27 03:39:45.10 spid7s index restored for msdb.sysjobs.
2014-09-27 03:39:45.10 spid7s index restored for msdb.sysutility_ucp_mi_file_space_health_internal.
2014-09-27 03:39:45.10 spid7s index restored for msdb.sysutility_ucp_mi_database_health_internal.
2014-09-27 03:39:45.10 spid7s index restored for msdb.syscollector_blobs_internal.
2014-09-27 03:39:45.11 spid7s index restored for msdb.sysutility_mi_dac_execution_statistics_internal.
2014-09-27 03:39:45.11 spid7s index restored for msdb.sysjobsteps.
2014-09-27 03:39:45.11 spid7s index restored for msdb.sysutility_ucp_dac_file_space_health_internal.
2014-09-27 03:39:45.11 spid7s index restored for msdb.logmarkhistory.
2014-09-27 03:39:45.11 spid7s index restored for msdb.sysutility_mi_session_statistics_internal.
2014-09-27 03:39:45.12 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.12 spid7s index restored for msdb.sysdtscategories.
2014-09-27 03:39:45.33 spid7s index restored for msdb.syspolicy_target_sets_internal.
2014-09-27 03:39:45.33 spid7s index restored for msdb.sysutility_ucp_mi_volume_space_health_internal.
2014-09-27 03:39:45.33 spid7s index restored for msdb.sysschedules.
2014-09-27 03:39:45.33 spid7s index restored for msdb.sysdac_instances_internal.
2014-09-27 03:39:45.33 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.50 spid7s index restored for msdb.sysssispackages.
2014-09-27 03:39:45.51 spid7s index restored for msdb.sysutility_ucp_computer_cpu_health_internal.
2014-09-27 03:39:45.51 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.52 spid7s index restored for msdb.sysssispackagefolders.
2014-09-27 03:39:45.52 spid7s index restored for msdb.sysdac_history_internal.
2014-09-27 03:39:45.53 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.62 spid7s index restored for msdb.syscategories.
2014-09-27 03:39:45.62 spid7s index restored for msdb.systargetservers.
2014-09-27 03:39:45.62 spid7s index restored for msdb.systargetservergroups.
2014-09-27 03:39:45.62 spid7s index restored for msdb.syspolicy_policy_category_subscriptions_internal.
2014-09-27 03:39:45.62 spid7s index restored for msdb.sysalerts.
2014-09-27 03:39:45.62 spid7s index restored for msdb.sysoperators.
2014-09-27 03:39:45.63 spid7s index restored for msdb.syspolicy_system_health_state_internal.
2014-09-27 03:39:45.63 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.63 spid7s index restored for msdb.syscollector_config_store_internal.
2014-09-27 03:39:45.65 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.65 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.65 spid7s index restored for msdb.sysmanagement_shared_server_groups_internal.
2014-09-27 03:39:45.66 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.66 spid7s index restored for msdb.sysutility_mi_smo_properties_to_collect_internal.
2014-09-27 03:39:45.66 spid7s index restored for msdb.sysmanagement_shared_registered_servers_internal.
2014-09-27 03:39:45.66 spid7s index restored for msdb.syscachedcredentials.
2014-09-27 03:39:45.79 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.79 spid7s index restored for msdb.syscollector_collection_sets_internal.
2014-09-27 03:39:45.79 spid7s index restored for msdb.sysutility_ucp_dac_health_internal.
2014-09-27 03:39:45.80 spid7s index restored for msdb.MSdbms.
2014-09-27 03:39:45.80 spid7s index restored for msdb.MSdbms_datatype.
2014-09-27 03:39:45.80 spid7s index restored for msdb.sysmail_profile.
2014-09-27 03:39:45.80 spid7s index restored for msdb.sysutility_ucp_managed_instances_internal.
2014-09-27 03:39:45.83 spid7s index restored for msdb.syspolicy_management_facets.
2014-09-27 03:39:45.84 spid7s index restored for msdb.sysutility_ucp_mi_health_internal.
2014-09-27 03:39:45.86 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.86 spid7s index restored for msdb.syscollector_collector_types_internal.
2014-09-27 03:39:45.86 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.86 spid7s index restored for msdb.syspolicy_configuration_internal.
2014-09-27 03:39:45.87 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.87 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.87 spid7s index restored for msdb.syspolicy_facet_events.
2014-09-27 03:39:45.87 spid7s index restored for msdb.sysmail_account.
2014-09-27 03:39:45.87 spid7s index restored for msdb.syspolicy_conditions_internal.
2014-09-27 03:39:45.88 spid7s index restored for msdb.sysutility_ucp_health_policies_internal.
2014-09-27 03:39:45.88 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.88 spid7s index restored for msdb.syscollector_collection_items_internal.
2014-09-27 03:39:45.90 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:46.00 spid7s index restored for msdb.sysmail_servertype.
2014-09-27 03:39:46.00 spid7s index restored for msdb.sysutility_ucp_filegroups_with_policy_violations_internal.
2014-09-27 03:39:46.02 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:46.03 spid7s index restored for msdb.sysutility_ucp_policy_check_conditions_internal.
2014-09-27 03:39:46.03 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:46.03 spid7s index restored for msdb.sysutility_ucp_configuration_internal.
2014-09-27 03:39:46.03 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:46.03 spid7s index restored for msdb.sysutility_ucp_policy_target_conditions_internal.
2014-09-27 03:39:46.04 spid7s index restored for msdb.sysmail_server.
2014-09-27 03:39:46.04 spid7s index restored for msdb.syspolicy_policy_categories_internal.
2014-09-27 03:39:46.04 spid7s index restored for msdb.syspolicy_object_sets_internal.
2014-09-27 03:39:46.04 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:46.05 spid7s index restored for msdb.sysmail_configuration.
2014-09-27 03:39:46.05 spid7s index restored for msdb.sysdbmaintplan_databases.
2014-09-27 03:39:46.05 spid7s index restored for msdb.log_shipping_primary_databases.
2014-09-27 03:39:46.39 spid7s The default collation was successfully changed.
2014-09-27 03:39:46.39 spid7s Recovery is complete. This is an informational message only. No user action is required.
2014-09-27 03:39:47.17 spid51 Changed database context to 'master'.
2014-09-27 03:39:47.18 spid51 Changed language setting to us_english.
2014-09-27 03:39:47.72 spid51 Setting database option RECOVERY to FULL for database model.
2014-09-27 03:39:47.84 spid51 Configuration option 'show advanced options' changed from 0 to 1. Run the RECONFIGURE statement to install.
2014-09-27 03:39:47.84 spid51 FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
2014-09-27 03:39:47.98 spid51 Configuration option 'default language' changed from 0 to 0. Run the RECONFIGURE statement to install.
2014-09-27 03:39:47.98 spid51 Configuration option 'default full-text language' changed from 1033 to 1033. Run the RECONFIGURE statement to install.
2014-09-27 03:39:47.98 spid51 FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
2014-09-27 03:39:47.98 spid51 Configuration option 'show advanced options' changed from 1 to 0. Run the RECONFIGURE statement to install.
2014-09-27 03:39:47.98 spid51 FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
2014-09-27 03:39:48.27 spid51 Error: 15007, Severity: 16, State: 1.
2014-09-27 03:39:48.27 spid51 '' is not a valid login or you do not have permission.
2014-09-27 03:51:25.13 Logon Error: 18456, Severity: 14, State: 8.
2014-09-27 03:51:25.13 Logon Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: <local machine>]
2014-09-27 03:51:32.67 Logon Error: 18456, Severity: 14, State: 8.
2014-09-27 03:51:32.67 Logon Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: <local machine>]
2014-09-27 03:51:42.11 Logon Error: 18456, Severity: 14, State: 5.
2014-09-27 03:51:42.11 Logon Login failed for user 'CAGATAY\cagatay (cagatay)'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2014-09-27 03:52:42.07 Logon Error: 18456, Severity: 14, State: 5.
2014-09-27 03:52:42.07 Logon Login failed for user 'CAGATAY\cagatay (cagatay)'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2014-09-27 03:53:01.23 Logon Error: 18461, Severity: 14, State: 1.
2014-09-27 03:53:01.23 Logon Login failed for user 'CAGATAY\cagatay'. Reason: Server is in single user mode. Only one administrator can connect at this time. [CLIENT: <local machine>]
2014-09-27 03:53:17.57 Logon Error: 18456, Severity: 14, State: 8.
2014-09-27 03:53:17.57 Logon Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: <local machine>]
2014-09-27 03:53:32.54 Logon Error: 18456, Severity: 14, State: 5.
2014-09-27 03:53:32.54 Logon Login failed for user 'CAGATAY\cagatay (cagatay)'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2014-09-27 03:54:04.29 Logon Error: 18456, Severity: 14, State: 5.
2014-09-27 03:54:04.29 Logon Login failed for user 'CAGATAY\cagatay (cagatay)'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2014-09-27 03:54:10.36 Logon Error: 18456, Severity: 14, State: 5.
2014-09-27 03:54:10.36 Logon Login failed for user 'CAGATAY\cagatay'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2014-09-27 03:54:47.18 Logon Error: 18456, Severity: 14, State: 8.
2014-09-27 03:54:47.18 Logon Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: <local machine>]
Resolve the error, please refer to the following links.
Enable DAC:http://www.mssqltips.com/sqlservertip/2538/enabling-dedicated-administrator-connection-in-sql-server-2008-express-edition/
could not register the SPN Kerberos:
http://saveadba.blogspot.com/2012/03/could-not-register-spn-kerberos.html
Make sure the password of sa is correct,and the login 'CAGATAY\cagatay' has been created in SQL Server

Unable to install Update Windows 7 x64-based system KB2952664

Unable to install Update Windows 7 x64-based system KB2952664, Error code 80073701. Internet Explorer 11 for Windows 7(although IE 11 is already installed) fails to install also(at the same time)

Hi,
Please try to do download oracle database 11.2.0.3.0 64 bit
Oracle Database 11.2.0.3.0 is certified on Microsoft Windows x64 (64-bit) 7
Thanks,
Rajasekhar

Installed FSCM 9.2 Demo w/ tools 8.53 on OEL 6, Oracle DB, Booted Web/App/Prcs ok, but error "Authorization Error -- Contact your Security AdministratorAuthorization" on page

Installed FSCM 9.2 Demo w/ tools 8.53 on OEL 6, Oracle DB, Booted Web/App/Prcs ok, but error "Authorization Error -- Contact your Security Administrator" on page. Has anyone encounter this issue. I have done most of the usual troubleshooting already.

Hi,
Roles linked to users are stored table psroleuser.
When I run following sql statement in my FSCM 9.2 demo env for user VP1, it returns 95 roles.
select * from psroleuser where roleuser = 'VP1';
And my environment is a ootb demo installation.
Here is an export of my config that you can try to load in your env, but something has definitely gone wrong for your env.
For a list of PeopleTools Security tables have a look at following blog
PeopleTools Security - PeopleSoft Wiki
REM INSERTING into psroleuser
Insert into psroleuser (ROLEUSER,ROLENAME,DYNAMIC_SW) values ('VP1','ADS Designer','N');
Insert into psroleuser (ROLEUSER,ROLENAME,DYNAMIC_SW) values ('VP1','PTF Administrator','N');
Insert into psroleuser (ROLEUSER,ROLENAME,DYNAMIC_SW) values ('VP1','PTF Editor','N');
Insert into psroleuser (ROLEUSER,ROLENAME,DYNAMIC_SW) values ('VP1','PTF User','N');
Insert into psroleuser (ROLEUSER,ROLENAME,DYNAMIC_SW) values ('VP1','Search Query Administrator','N');
Insert into psroleuser (ROLEUSER,ROLENAME,DYNAMIC_SW) values ('VP1','PeopleTools','N');
Insert into psroleuser (ROLEUSER,ROLENAME,DYNAMIC_SW) values ('VP1','Catalog Partner','N');
Insert into psroleuser (ROLEUSER,ROLENAME,DYNAMIC_SW) values ('VP1','CC_ADMINISTRATOR','N');
Insert into psroleuser (ROLEUSER,ROLENAME,DYNAMIC_SW) values ('VP1','CC_USER_PO','N');
Insert into psroleuser (ROLEUSER,ROLENAME,DYNAMIC_SW) values ('VP1','CC_USER_REQ','N');
Insert into psroleuser (ROLEUSER,ROLENAME,DYNAMIC_SW) values ('VP1','CLAIMS_MGR','N');
Insert into psroleuser (ROLEUSER,ROLENAME,DYNAMIC_SW) values ('VP1','CLERK','N');
Insert into psroleuser (ROLEUSER,ROLENAME,DYNAMIC_SW) values ('VP1','XMLP Power User','N');
Insert into psroleuser (ROLEUSER,ROLENAME,DYNAMIC_SW) values ('VP1','VMI Manager','N');
Insert into psroleuser (ROLEUSER,ROLENAME,DYNAMIC_SW) values ('VP1','XMLP Report Developer','N');
Insert into psroleuser (ROLEUSER,ROLENAME,DYNAMIC_SW) values ('VP1','SP_EXPENSE_APPROVER','N');
Insert into psroleuser (ROLEUSER,ROLENAME,DYNAMIC_SW) values ('VP1','SP_INV_APPROVER','N');
Insert into psroleuser (ROLEUSER,ROLENAME,DYNAMIC_SW) values ('VP1','EOEN_USER','N');
Insert into psroleuser (ROLEUSER,ROLENAME,DYNAMIC_SW) values ('VP1','ePro Buyer','N');
Insert into psroleuser (ROLEUSER,ROLENAME,DYNAMIC_SW) values ('VP1','ePro Admin','N');
Insert into psroleuser (ROLEUSER,ROLENAME,DYNAMIC_SW) values ('VP1','Search Administrator','N');
Insert into psroleuser (ROLEUSER,ROLENAME,DYNAMIC_SW) values ('VP1','Search Developer','N');
Insert into psroleuser (ROLEUSER,ROLENAME,DYNAMIC_SW) values ('VP1','Search Server','N');
Insert into psroleuser (ROLEUSER,ROLENAME,DYNAMIC_SW) values ('VP1','IT Asset Manager','N');
Insert into psroleuser (ROLEUSER,ROLENAME,DYNAMIC_SW) values ('VP1','ITEMLOAD_CONTACT','N');
Insert into psroleuser (ROLEUSER,ROLENAME,DYNAMIC_SW) values ('VP1','MANAGER','N');
Insert into psroleuser (ROLEUSER,ROLENAME,DYNAMIC_SW) values ('VP1','PAPP_USER','N');
Insert into psroleuser (ROLEUSER,ROLENAME,DYNAMIC_SW) values ('VP1','PBM User','N');
Insert into psroleuser (ROLEUSER,ROLENAME,DYNAMIC_SW) values ('VP1','PeopleSoft User','N');
Insert into psroleuser (ROLEUSER,ROLENAME,DYNAMIC_SW) values ('VP1','EMPLOYEE','N');
Insert into psroleuser (ROLEUSER,ROLENAME,DYNAMIC_SW) values ('VP1','Employee North America','N');
Insert into psroleuser (ROLEUSER,ROLENAME,DYNAMIC_SW) values ('VP1','Ent Utilities Administrator','N');
Insert into psroleuser (ROLEUSER,ROLENAME,DYNAMIC_SW) values ('VP1','EOPP_USER','N');
Insert into psroleuser (ROLEUSER,ROLENAME,DYNAMIC_SW) values ('VP1','Event Buyer','N');
Insert into psroleuser (ROLEUSER,ROLENAME,DYNAMIC_SW) values ('VP1','Event Seller','N');
Insert into psroleuser (ROLEUSER,ROLENAME,DYNAMIC_SW) values ('VP1','Forecaster','N');
Insert into psroleuser (ROLEUSER,ROLENAME,DYNAMIC_SW) values ('VP1','Grants Super User','N');
Insert into psroleuser (ROLEUSER,ROLENAME,DYNAMIC_SW) values ('VP1','EX_EMPLOYEE','N');
Insert into psroleuser (ROLEUSER,ROLENAME,DYNAMIC_SW) values ('VP1','MIN Adminstrator','N');
Insert into psroleuser (ROLEUSER,ROLENAME,DYNAMIC_SW) values ('VP1','Connected Queries Developer','N');
Insert into psroleuser (ROLEUSER,ROLENAME,DYNAMIC_SW) values ('VP1','PeopleSoft Administrator','N');
Insert into psroleuser (ROLEUSER,ROLENAME,DYNAMIC_SW) values ('VP1','Integration Administrator','N');
Insert into psroleuser (ROLEUSER,ROLENAME,DYNAMIC_SW) values ('VP1','Supplier Contract Interested','N');
Insert into psroleuser (ROLEUSER,ROLENAME,DYNAMIC_SW) values ('VP1','Supplier-Application Admin','N');
Insert into psroleuser (ROLEUSER,ROLENAME,DYNAMIC_SW) values ('VP1','UPG_ALLPNLS','N');
Insert into psroleuser (ROLEUSER,ROLENAME,DYNAMIC_SW) values ('VP1','UPG_APPSRVR','N');
Insert into psroleuser (ROLEUSER,ROLENAME,DYNAMIC_SW) values ('VP1','VICE PRESIDENT','N');
Insert into psroleuser (ROLEUSER,ROLENAME,DYNAMIC_SW) values ('VP1','System Administrator','N');
Insert into psroleuser (ROLEUSER,ROLENAME,DYNAMIC_SW) values ('VP1','Treasurer','N');
Insert into psroleuser (ROLEUSER,ROLENAME,DYNAMIC_SW) values ('VP1','EOTF_ADMIN','N');
Insert into psroleuser (ROLEUSER,ROLENAME,DYNAMIC_SW) values ('VP1','ProcessSchedulerAdmin','N');
Insert into psroleuser (ROLEUSER,ROLENAME,DYNAMIC_SW) values ('VP1','Project Owner','N');
Insert into psroleuser (ROLEUSER,ROLENAME,DYNAMIC_SW) values ('VP1','Grants Workflow By Pass','N');
Insert into psroleuser (ROLEUSER,ROLENAME,DYNAMIC_SW) values ('VP1','Inventory Policy Planner','N');
Insert into psroleuser (ROLEUSER,ROLENAME,DYNAMIC_SW) values ('VP1','CONSUMER','N');
Insert into psroleuser (ROLEUSER,ROLENAME,DYNAMIC_SW) values ('VP1','DEALING MANAGER','N');
Insert into psroleuser (ROLEUSER,ROLENAME,DYNAMIC_SW) values ('VP1','PivotGridAdmin','N');
Insert into psroleuser (ROLEUSER,ROLENAME,DYNAMIC_SW) values ('VP1','PTLT_IMPLEMENTER','N');
Insert into psroleuser (ROLEUSER,ROLENAME,DYNAMIC_SW) values ('VP1','PTLT_INTERNAL_APPS','N');
Insert into psroleuser (ROLEUSER,ROLENAME,DYNAMIC_SW) values ('VP1','Translation Utilities','N');
Insert into psroleuser (ROLEUSER,ROLENAME,DYNAMIC_SW) values ('VP1','ADMINISTRATOR','N');
Insert into psroleuser (ROLEUSER,ROLENAME,DYNAMIC_SW) values ('VP1','AM_SS_ACCOUNTING_CLERK','N');
Insert into psroleuser (ROLEUSER,ROLENAME,DYNAMIC_SW) values ('VP1','PTLT_PROJECT_MGR','N');
Insert into psroleuser (ROLEUSER,ROLENAME,DYNAMIC_SW) values ('VP1','RE_ADMIN','N');
Insert into psroleuser (ROLEUSER,ROLENAME,DYNAMIC_SW) values ('VP1','Security Administrator','N');
Insert into psroleuser (ROLEUSER,ROLENAME,DYNAMIC_SW) values ('VP1','SETTLEMENT_MGR','N');
Insert into psroleuser (ROLEUSER,ROLENAME,DYNAMIC_SW) values ('VP1','SP_ADMINISTRATOR','N');
Insert into psroleuser (ROLEUSER,ROLENAME,DYNAMIC_SW) values ('VP1','SP_APPROVER','N');
Insert into psroleuser (ROLEUSER,ROLENAME,DYNAMIC_SW) values ('VP1','SP_COORDINATOR','N');
Insert into psroleuser (ROLEUSER,ROLENAME,DYNAMIC_SW) values ('VP1','SP_EXECUTIVE','N');
Insert into psroleuser (ROLEUSER,ROLENAME,DYNAMIC_SW) values ('VP1','RE_SUPER','N');
Insert into psroleuser (ROLEUSER,ROLENAME,DYNAMIC_SW) values ('VP1','EOTL_Admin','N');
Insert into psroleuser (ROLEUSER,ROLENAME,DYNAMIC_SW) values ('VP1','SP_INVOICE_MANAGER','N');
Insert into psroleuser (ROLEUSER,ROLENAME,DYNAMIC_SW) values ('VP1','SP_PLOG_APPROVER','N');
Insert into psroleuser (ROLEUSER,ROLENAME,DYNAMIC_SW) values ('VP1','SP_PROVIDER','N');
Insert into psroleuser (ROLEUSER,ROLENAME,DYNAMIC_SW) values ('VP1','SP_PROVIDER_CONTACT','N');
Insert into psroleuser (ROLEUSER,ROLENAME,DYNAMIC_SW) values ('VP1','SP_REQUESTER','N');
Insert into psroleuser (ROLEUSER,ROLENAME,DYNAMIC_SW) values ('VP1','SP_TIME_APPROVER','N');
Insert into psroleuser (ROLEUSER,ROLENAME,DYNAMIC_SW) values ('VP1','SP_WO_APPROVER','N');
Insert into psroleuser (ROLEUSER,ROLENAME,DYNAMIC_SW) values ('VP1','SUPERVISOR','N');
Insert into psroleuser (ROLEUSER,ROLENAME,DYNAMIC_SW) values ('VP1','Supplier Contrct Administrator','N');
Insert into psroleuser (ROLEUSER,ROLENAME,DYNAMIC_SW) values ('VP1','Demand Planner','N');
Insert into psroleuser (ROLEUSER,ROLENAME,DYNAMIC_SW) values ('VP1','Employee','N');
Insert into psroleuser (ROLEUSER,ROLENAME,DYNAMIC_SW) values ('VP1','Plan Approver','N');
Insert into psroleuser (ROLEUSER,ROLENAME,DYNAMIC_SW) values ('VP1','Portal Administrator','N');
Insert into psroleuser (ROLEUSER,ROLENAME,DYNAMIC_SW) values ('VP1','ReportSuperUser','N');
Insert into psroleuser (ROLEUSER,ROLENAME,DYNAMIC_SW) values ('VP1','AM_SS_MANAGER','N');
Insert into psroleuser (ROLEUSER,ROLENAME,DYNAMIC_SW) values ('VP1','App Developer','N');
Insert into psroleuser (ROLEUSER,ROLENAME,DYNAMIC_SW) values ('VP1','BAM Administrator','N');
Insert into psroleuser (ROLEUSER,ROLENAME,DYNAMIC_SW) values ('VP1','BANK MANAGER','N');
Insert into psroleuser (ROLEUSER,ROLENAME,DYNAMIC_SW) values ('VP1','Budget Approver','N');
Insert into psroleuser (ROLEUSER,ROLENAME,DYNAMIC_SW) values ('VP1','Call Center Agent','N');
Insert into psroleuser (ROLEUSER,ROLENAME,DYNAMIC_SW) values ('VP1','Call Center Specialist','N');
Insert into psroleuser (ROLEUSER,ROLENAME,DYNAMIC_SW) values ('VP1','Cash Manager','N');
Insert into psroleuser (ROLEUSER,ROLENAME,DYNAMIC_SW) values ('VP1','Catalog Administrator','N');

How to install 4.6 B on my system.

i am trying to install 4.6 B on my system but do not have any installation guide. so can you guys help me out with that.
thanx
regards
Jawad

Hi,
Always the best would be from http://service.sap.com. Any how i am trying to give it in a nutshell.
1) installation of Windows 2000 on a PC Harddisk 120 GB, 512 ram)
Question: - it is IDES 4.6B in the installation guide they say it runs on Windows NT does it run on Windows 2000 to? need to install service packs on windows 2000?
2) installation oracle 8.0.5 patch 8.0.5.2.2 listener in the services should be running
3) run the kernel cd :\NT\COMMON\R3setup.bat:
4) Install the central instance using the standard template CENTRAL.R3S
5) copy the install script DB_IDES.R3S to DATABASE.R3S
6) run the installation
Feel free to revert back.
--Ragu

Can't open database with Windows from linux system *URGENT*

Hi,
i've two systems. A Linux SuSE 9.3 Pro system with Oracle Database 9.2.0.4
and a Windows 2000 system with the same version of Oracle.
Now, i try to connect the Windows system with the Linux system, but i doesn't work. I also, have
installed the Listener, on the linux system.
What am i doing wrong? Can someone help me?
Thanks in advance.
Greets
Daniel

Thanks, but i've already solved the problem.
I've just switched off the firewall on the linux system.
And now it works.
But thanks for ur reply.

Connections to CMS/AUDIT system Databases lost

we are often losing connection to CMS/AUDIT system Databases therefore
users can not log into Infoview.
The work around is to restart the Server Intelligence Agent (sia.exe)
Server Details: we have BusObjects Edge standard XI 3.0
Application Server: MS Windows Server 2003 Standard Edition SP2
Database Server: MS Windows Server 2003 Standard Edition SP2
There are multiple errors in our event viewer showing these errors.
They have been happening for the last week.
Not sure why this is happening or how to reproduce anyone know how to fix?
Event viewer > application details:
Event Type:      Error
Event Source:   BusinessObjects_CMS
Event Category:            Database
Description:
BusinessObjects Enterprise CMS: All connections to CMS system database ""BO_CMS"" have been lost. The CMS is entering the ""Waiting For Resources"" state. Reason [Microsoft][ODBC SQL Server Driver]Communication link failure
Description:
BusinessObjects Enterprise CMS: All connections to CMS audit database ""BO_AUDIT"" have been lost. The CMS can no longer serve as Auditor. Reason: [Microsoft][ODBC SQL Server Driver]Communication link failure
Edited by: Dennis Alishah on Dec 15, 2010 11:37 PM

no network problems
thanks
Found this is the SAP SMP I also asked them waiting for their reply to see if the below fix is suitable:
SAP Knowledge Base Article
Symptom
CMS restarts and throws Database access error. Reason [Microsoft][ODBC SQL Server Driver]Communication link failure in the event viewer.
BusinessObjects_CMS,Warning,Database ,33300,N/A,GADEVBO1,Database access error. Reason [Microsoft][ODBC SQL Server Driver]Communication link failure.
BusinessObjects_CMS,Warning,Database ,33301,N/A,GADEVBO1,Retryable error returned from CMS database. Will retry the request 3 time(s).
BusinessObjects_CMS,Warning,Database ,33300,N/A,GADEVBO1,Database access error. Reason [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionWrite
Cause
The error occurs because Microsoft Windows Server 2003 Service Pack 1 (SP1) and Windows Server 2003 Service Pack 2 (SP2) implement a security feature that the queue for concurrent TCP/IP connections to the server. This feature helps prevent denial of service attacks.
Under heavy load conditions, the TCP/IP protocol in Windows Server 2003 SP1 and in Windows Server 2003 SP2 may incorrectly identify valid TCP/IP connections service attack.
Resolution
WARNING *** The following resolution involves editing the registry. Using the Registry Editor incorrectly can cause serious Use the Registry Editor at your own risk. Refer to Note 1323322 for more information.
To resolve this issue, turn off this new functionality in Windows Server 2003 SP1 or in Windows Server 2003 SP2 by adding the SynAttackProtect entry to the following registry computer that is running Microsoft SQL Server that houses your BizTalk Server databases.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
Set the SynAttackProtect entry to a DWORD value of 00000000.
To do this, follow these steps:
1. Click Start, click Run, type regedit, and then click OK.
2. Locate and then click the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
3. On the Edit menu, point to New, and then click DWORD Value.
4. Type SynAttackProtect, and then press ENTER.
5. On the Edit menu, click Modify.
6. In the Value data box, type 00000000. Click OK.
7. Quit Registry Editor.
Note To complete this registry change, you must restart the computer that is running SQL Server.
See Also
For detailed information, go to the following Microsoft website:
http://support.microsoft.com/default.aspx?scid=kb;en-us;899599
Header Data
References
Product
1375277 - CMS lost the SQLServer 2000/2005 communication and restarts intermittently
Version 1 Validity: 12.08.2009 - active Language English
Released on 07.10.2009 15:35:25
Release status Released to Customer
Component BI-BIP-ADM User & server configuration, InfoView refresh, user rights
Priority Normal
Category Problem
Database MSSQLSRV 2005
Operating System WIN 2003
Type ID Title
Business Objects Notes 1323322 Editing the Windows Registry - Warning
Product Product Version
SAP BusinessObjects Business Intelligence platform (formerly SB BOBJ ENTERPRISE XI R2
1375277 - CMS lost the SQLServer 2000/2005 communication and restarts intermitte... Page 1 of 1
https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/sno/ui/main.do?para... 16/12/2010
Edited by: Dennis Alishah on Dec 16, 2010 12:23 AM

Copy Orace file-system database to ASM

Hi,
We are planning to use ASM and migrate of file-system database
How do you move/copy oracle datafiles,logfiles,controlfiles,*.dbf to ASM?
The docs said ASM does not allow OS copy commands :(
Thanks a lot

Thanks a lot Hussein, Arnoud :) I like those docs very short/summarized and easy to understand, unlike other oracle manuals which gives you lots of choices/platforms/versions/ and confusion mixed in one.
By the way I am planning to install a new set of 64-bit EBS R12 on ASM/RAC and leave alone our EBS R12 32bit(filesytem) running. I dont like to migrate it because it so critical
and sensitive to touch.
Just a little clarification :).....When I run EBS R12 installer (database tier side) It ask for
home directories like: /u01/app/orace
My question is I want my database files (.dbf) to be directed to an ASM disk
How do I input it in the Rapidwiz installer? I did not see any options there to use ASM disk.
Thanks again

Identify installed database is a DEMO or SYSTEM database

Similar Messages

Maybe you are looking for