"Error restoring Databases" SMS import failing!
Hey all-
I keep getting an "error restoring databases" message when trying to put all of the SMS texts from my Curve 8330 onto my World Edition. I did this yesterday and it worked fine. The problem is the screen on my curve is dead so until I get a new one, I have to keep making backup files and uploading them onto my world edition so I can see my texts/phone calls that I've been receiving on the curve.
I managed to do this successfully yesterday morning but since then I keep getting this error message. I have tried clearing the SMS on the World then pulling in just the SMS from the backup file, full deviced transfers and partial/full restores! All of them are giving me the same "error restoring databases" and it may pull in a few of the 1334 texts I have to import.
Both Blackberrys are up to date OS-wise and BB Desktop Manager is v5
Any help would be appreciated!!! THANKS
Hi,
The IMP indicates this this error is coming from the old imp. This dump file could be from the expdp utility, which would require you to use the impdp utility.
Source
OS : Solaris 10
Oracle version : 11.2.0.2
Export dump : exp_CAAU2.dmp.gz (Export taken by zipping)
Target
OS : Windows server 2003
Oracle Version : 10.2.0.2.0
While importing into windows env, it is failing..
What really matters here is the compatibility level. If your source and target compatibility levels are the same, then with Data Pump, the dumpfile created on the source, would work on the target. If the compatibility levels are different, then use expdp with the version parameter set to the compatibility level of the target.
Please let me know the reason why the import is failing?Check the suggestions above first.
Can i upgrade the target oracle version to 11.2.0.2 to succeed the import?It could help, but first check to see if you are using the right utility and then check the compatibility versions.
Dean
Similar Messages
-
RMAN Error - restore database validate
Hi all
I am trying to validate a full database backup taken on tape using 'restore database validate' command but for some reason this command spits out multi-page long PL/SQL code (below truncated output). I have searched all over for a solution but can't seem to figure out the problem.
Any assistance will be appreciated.
RMAN> allocate channel for maintenance type SBT_TAPE parms 'ENV=(TDPO_OPTFILE=/opt/tivoli/tsm/client/oracle/bin64/tdpo.opt)';
2> crosscheck backup;
3> restore database validate;
4> release channel;
5> exit;
allocated channel: ORA_MAINT_SBT_TAPE_1
channel ORA_MAINT_SBT_TAPE_1: SID=82 device type=SBT_TAPE
channel ORA_MAINT_SBT_TAPE_1: Data Protection for Oracle: version 5.4.1.0
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=c-822607628-20101006-02 RECID=66 STAMP=731711718
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=DB_20101007_77_2dlpsj84_1_1.dbf RECID=67 STAMP=731794692
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=CF_20101008_116_3klpt5iv_1_1.ctl RECID=106 STAMP=731813472
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=c-822607628-20101008-01 RECID=107 STAMP=731813518
Crosschecked 42 objects
Starting restore at 08-OCT-10
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=110 device type=DISK
DBGANY: CMD type=IRESTORE cmdid=1 status=NOT STARTED
DBGANY: 1 STEPstepid=1 cmdid=1 status=NOT STARTED devtype=SBT_TAPE bs.stamp=731812991 step_size=0 Bytes
DBGANY: 1 TEXTNOD = -- rsdf_start
DBGANY: 2 TEXTNOD = declare
DBGANY: 3 TEXTNOD = /* restoreStatus */
DBGANY: 4 TEXTNOD = state binary_integer;
DBGANY: 5 TEXTNOD = pieces_done binary_integer;
DBGANY: 6 TEXTNOD = files binary_integer;
DBGANY: 7 TEXTNOD = datafiles boolean;
DBGANY: 8 TEXTNOD = incremental boolean;
DBGANY: 9 TEXTNOD = device boolean;
DBGANY: 10 TEXTNOD = /* restorebackuppiece */
DBGANY: 11 TEXTNOD = done boolean;
DBGANY: 12 TEXTNOD = currcf boolean;
DBGANY: 266 TEXTNOD = sys.dbms_backup_restore.restoreCancel(FALSE);
DBGANY: 267 TEXTNOD = exception
DBGANY: 268 TEXTNOD = when others then
DBGANY: 269 TEXTNOD = krmicd.writeMsg(1005,
DBGANY: 270 TEXTNOD = 'c. dbms_backup_restore.restoreCancel() failed');
DBGANY: 271 TEXTNOD = end;
DBGANY: 272 TEXTNOD = sys.dbms_backup_restore.setRmanStatusRowId(rsid=>0, rsts=>0);
DBGANY: 273 TEXTNOD = end;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00601: fatal error in recovery manager
RMAN-03004: fatal error during execution of command
RMAN-00600: internal error, arguments [6000] [] [] [] []Hi Sybrand
So here's the deal:
1) 'backup validate database;' is run before RMAN backup to check for any logical or physical corruption in datafiles or archivelogs.
If the backup validation discovers corrupt blocks, then RMAN updates the V$DATABASE_BLOCK_CORRUPTION view with rows describing the corruptions.
2)
a- 'restore database validate;' is run after RMAN backup to check for any logical or physical corruption in backupsets.
b- 'validate backupset <n>;' is also run after RMAN backup to check for any logical or physical corruption in backupsets. The difference being you have to run it for each individual backupset as opposed to the previous option (2a), which loops through all existing backupsets.
I believe for now only option 2b is available for use in my case.
Cheers. -
Orcale Database Assistant Install Fails
When conducting a typical enterprise install for 8i under
RedHat Linux 6.1 I receive the following error :
Oracle Database Configuration Assistant failed
A required command line argument is missing.
My enviornment seems to be set up correctly, any
suggestions would be appreciated.
Scott
nullCharles Hill (guest) wrote:
: Scott Brause (guest) wrote:
: : When conducting a typical enterprise install for 8i
under
: : RedHat Linux 6.1 I receive the following error :
: : Oracle Database Configuration Assistant failed
: : A required command line argument is missing.
: : My enviornment seems to be set up correctly, any
: : suggestions would be appreciated.
: : Scott
: I got that message, too. I did not resolve it yet.
Charles,
I managed to solve this one. In fact I wrote a note back
to myself on this discussion but evidentally I didn't send it.
Now if I can just remember the solution...
I believe the problem was that I didn't have ORACLE/BIN in
my path or one of the necessary enviornment variables were not
set an exported here are the important things I added to my
profile...
PATH=$PATH:$HOME/bin:$ORACLE_HOME/bin:usr/bin:/usr/local/bin
ORACLE_BASE=/usr/oracle/u01/app/oracle
ORACLE_HOME=$ORACLE_BASE/product/release
LD_LIBRARY_PATH=$ORACLE_HOME/lib
ORACLE_SID=dev
ORACLE_SID was the name of my database. The answer to this
question was in the FAQ or release notes but skimming through
it, it didn't stand out like it did a few days ago.
Hope this helps.
Scott
null -
Hello,
I am trying to install Microsoft SQL Server 2008 R2. I get the error bellow (Database Services Engine Failed, SQL Server Replication Failed, Full Text Search Failed, Reporting Services Failed). I already have a copy of SQL Server 2008 R2 on the machine.
I want to create a new named instance of SQL Server for some software I'm installing.
The error is below.
Any help would be much appreciated, thanks!
Overall summary:
Final result: SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then
rerun SQL Server Setup.
Exit code (Decimal): -595541211
Exit facility code: 1152
Exit error code: 49957
Exit message: SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then
rerun SQL Server Setup.
Start time: 2014-02-06 09:14:09
End time: 2014-02-06 11:18:16
Requested action: Install
Log with failure: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140206_091302\Detail.txt
Exception help link: http%3a%2f%2fgo.microsoft.com%2ffwlink%3fLinkId%3d20476%26ProdName%3dMicrosoft%2bSQL%2bServer%26EvtSrc%3dsetup.rll%26EvtID%3d50000%26ProdVer%3d10.50.2500.0%26EvtType%3d0x44D4F75E%400xDC80C325
Machine Properties:
Machine name: BAHPBZ52TY
Machine processor count: 4
OS version: Windows 7
OS service pack: Service Pack 1
OS region: United States
OS language: English (United States)
OS architecture: x64
Process architecture: 64 Bit
OS clustered: No
Product features discovered:
Product Instance Instance ID
Feature Language
Edition Version Clustered
Sql Server 2008 R2 SQLEXPRESS MSSQL10_50.SQLEXPRESS Database Engine Services
1033 Express Edition 10.50.1600.1 No
Sql Server 2008 R2
Management Tools - Basic 1033 Express Edition
10.50.1600.1 No
Package properties:
Description: SQL Server Database Services 2008 R2
ProductName: SQL Server 2008 R2
Type: RTM
Version: 10
Installation location: c:\c7ced2c86d6b9813b28186cc831c2054\x64\setup\
Installation edition: EXPRESS_ADVANCED
Slipstream: True
SP Level 1
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: True
AGTSVCACCOUNT: NT AUTHORITY\NETWORK SERVICE
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Disabled
ASBACKUPDIR: Backup
ASCOLLATION: Latin1_General_CI_AS
ASCONFIGDIR: Config
ASDATADIR: Data
ASDOMAINGROUP: <empty>
ASLOGDIR: Log
ASPROVIDERMSOLAP: 1
ASSVCACCOUNT: <empty>
ASSVCPASSWORD: *****
ASSVCSTARTUPTYPE: Automatic
ASSYSADMINACCOUNTS: <empty>
ASTEMPDIR: Temp
BROWSERSVCSTARTUPTYPE: Disabled
CONFIGURATIONFILE:
CUSOURCE:
ENABLERANU: True
ENU: True
ERRORREPORTING: False
FARMACCOUNT: <empty>
FARMADMINPORT: 0
FARMPASSWORD: *****
FEATURES: SQLENGINE,REPLICATION,FULLTEXT,RS,SSMS,SNAC_SDK,OCS
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME: <empty>
FTSVCACCOUNT: NT AUTHORITY\LOCAL SERVICE
FTSVCPASSWORD: *****
HELP: False
INDICATEPROGRESS: False
INSTALLSHAREDDIR: c:\Program Files\Microsoft SQL Server\
INSTALLSHAREDWOWDIR: c:\Program Files (x86)\Microsoft SQL Server\
INSTALLSQLDATADIR: <empty>
INSTANCEDIR: C:\Program Files\Microsoft SQL Server\
INSTANCEID: aedt2bSQL
INSTANCENAME: AEDT2BSQL
ISSVCACCOUNT: NT AUTHORITY\NetworkService
ISSVCPASSWORD: *****
ISSVCSTARTUPTYPE: Automatic
NPENABLED: 0
PASSPHRASE: *****
PCUSOURCE: c:\c7ced2c86d6b9813b28186cc831c2054\PCUSOURCE
PID: *****
QUIET: False
QUIETSIMPLE: False
ROLE: AllFeatures_WithDefaults
RSINSTALLMODE: DefaultNativeMode
RSSVCACCOUNT: NT AUTHORITY\NETWORK SERVICE
RSSVCPASSWORD: *****
RSSVCSTARTUPTYPE: Automatic
SAPWD: *****
SECURITYMODE: SQL
SQLBACKUPDIR: <empty>
SQLCOLLATION: SQL_Latin1_General_CP1_CI_AS
SQLSVCACCOUNT: NT AUTHORITY\NETWORK SERVICE
SQLSVCPASSWORD: *****
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: BAH\568385
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: False
TCPENABLED: 0
UIMODE: AutoAdvance
X86: False
Configuration file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140206_091302\ConfigurationFile.ini
Detailed results:
Feature: Database Engine Services
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Failed: see details below
Configuration error code: 0xDC80C325
Configuration error description: Access is denied
Configuration log: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140206_091302\Detail.txt
Feature: SQL Client Connectivity SDK
Status: Passed
MSI status: Passed
Configuration status: Passed
Feature: SQL Server Replication
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Failed: see details below
Configuration error code: 0xDC80C325
Configuration error description: Access is denied
Configuration log: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140206_091302\Detail.txt
Feature: Full-Text Search
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Failed: see details below
Configuration error code: 0xDC80C325
Configuration error description: Access is denied
Configuration log: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140206_091302\Detail.txt
Feature: Reporting Services
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Failed: see details below
Configuration error code: 0xDC80C325
Configuration error description: Access is denied
Configuration log: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140206_091302\Detail.txt
Feature: Management Tools - Basic
Status: Passed
MSI status: Passed
Configuration status: Passed
Feature: Microsoft Sync Framework
Status: Passed
MSI status: Passed
Configuration status: Passed
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140206_091302\SystemConfigurationCheck_Report.htmHello,
If you see error descriptioon it gives access denied so basically it is because of some access issue.I guess You must be using some domin account for installation make sure it is added as local administrator also instead of using NT Authority network
service as SQL server service account use local system account .
Below link would help
http://serverfault.com/questions/212135/access-is-denied-error-installing-sql-server-2008-on-windows-7
You can also browse to setup.exe file and RK on it and select run as administrator
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers -
Data Services 12.2.3.0 BODI-1112015 Adapter metadata import failed
Hi Experts,
I am using Data Services 12.2.3.0.
I have an issue in importing functions through 'Adapter' type datastore into Data Services. I can open the datastore and see the list of functions available, but when I try to import them, I get the error BODI-1112015 Adapter metadata import failed.
The setup and the errors are as below.
The adapter datastore is setup as below.
I built a new keystore called clientkeystore.jks in the ..\bin.Then created the .CSR file, and then imported the signed chained (I believe it's chained certificate) certificate of the server hosting the wsdl into the keystore.
Thanks for the post http://scn.sap.com/thread/1589052 . After changing the metadata character set to utf-8, I can see a list of functions when I open this New_Datastore in Data Services. It proves that the setup for the datastore has no problem parsing the wsdl file and give me the list of functions in it.
However, the error appears when I try to import them.
Error is:
Adapter metadata import failed. Error message: (BODI-1112015) Error parsing the <TheFunctionToBeImported> included in the XML sent by the adapter to represet a function <Error importing XML Schema from file <adapter_schema_in.xsd>:<XML parser failed: Error <Schema Representation Constraint: Namespace 'http://result.form.v81.api.keysurvey.com' is referenced without <import> declaration> at line <13>, char <46> in < < xsd:schema xmln:xsd=http://www.w3.org/2001/XMLSchema" xmln:tns="http://result.form.v81.api.keystore.com" xmlns:diws="http://businessobjects.com/diwebservice" targetnamespace="http://www.businessobjects.com/diwebservice"><xsd:import namespace='http://v81.api.keysurvey.com' schemaLocation='C:\Program Files\Business Objects\BusinessObjects Data Services\ext\webservice\FormResultManagemenetgetRespondentsgetRespondents0.xsd'/>
<xsd: import namespace='http://result.form.v81.api.keysurvey.com' schemaLocation='C:\Program Files\Business Objects\BusinessObjects Data Services\ext\webservice\FormResultManagemenetgetRespondentsgetRespondents2.xsd'/> ........
When comparing it with the wsdl file(as below), it is worth nothing that the schemaLocation is changed to a local directory under C:\Program Files\Business Objects\BusinessObjects Data Services\ext\webservice while it was not the case in wsdl. The schemaLocation is on the server.
I am wondering if the redirection from the server specified in the wsdl file to the local directory has caused this error. The error 'namespace is reference without <import>' is apparently wrong as the <import> is just there.
Or there is any other reason behind this.
I appreciate any adivce or question from you!I have reached the exact same error as this post http://scn.sap.com/thread/3190403
The error is
[Mon Jun 18 23:14:28 2012] [error] ..\..\src\core\deployment\conf_builder.c(876) Specifyingservices and modules directories using axis2.xml but path of the library directory is not present
[Mon Jun 18 23:14:28 2012] [error] ..\..\src\core\deployment\conf_builder.c(261) Processing transport senders failed, unable to continue
[Mon Jun 18 23:14:28 2012] [error] ..\..\src\core\deployment\dep_engine.c(939) Populating Axis2 Configuration failed
[Mon Jun 18 23:14:28 2012] [error] ..\..\src\core\deployment\conf_init.c(195) Loading deployment engine failed for client repository C:\Program Files (x86)\SAP BusinessObjects\Data Services\ext\webservice-c\axis2.xml
As it is identified as an version problem, this issue is not going to be investigated any further.
As an alternative, can try to use Oracle 11g SOAP_API.sql. -
Thanks in advance for taking the time to read this and comment. Platform: Windows Server 2008 R2 Enterprise Edition SP1 (X64) Microsoft SQL Server 2008 R2 (SP1) - 10.50.2500.0 (X64) Jun 17 2011 00:54:03 Copyright (c) Microsoft Corporation
Standard Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1)Problem Description: The file name recorded in the msdb.dbo.backupset (sans the extension) no longer matches the actual file name written to the backup media which is
in this case a NETAPP NAS storage share. Example:
Mohave_backup_2014_03_14_233001_1158878.bak (from NETAPP NAS filer)
Mohave_backup_2014_03_16_233001_4167237 (from MSDB.dbo.backupset), as you can see, the last 7 digits (chars) of the file name are different, although the date and time are identical. The
file names had previously been matching perfectly. The first occurance of this problem occured on 03/13/2014 at 5:00 AM MST. The error generated by the job was:
Date 3/14/2014 10:29:23 AM
Log Job History (Refresh - Restore Mohave_93_DEV AD HOC)
Step ID 1
Server OurDevServer
Job Name Refresh - Restore Mohave_93_DEV AD HOC
Step Name Restore Mohave_93_DEV
Duration 00:00:01
Sql Severity 0
Sql Message ID 50000
Operator Emailed
Operator Net sent
Operator Paged
Retries Attempted 0
Message
Executed as user: OurDomain\OurNetworkServiceLogin. Restore Mohave Prod to Mohave_93_DEV - ERROR: 3013 RESTORE DATABASE is terminating abnormally. [SQLSTATE 01000] (Message 50000). The step succeeded.Olaf:
Thanks for your reply. Sorry, my bad. I inadvertently copied wrong [name] form the msdb.dbo.backupset. On 3/13 and 3/14, the two file names did not match. In trying to select another example to show you this morning, I found that the names are now matching!
What I was doing was to create dynamic t-sql to retrieve the latest prod backup of the database, and then restore it with move to the development server. This is an ad-hoc job that the developers can run by themselves whenever they require a refresh. Unfortunately,
we only keep 3 days worth of backups for these databases, so the original disk file I was trying to use to restore no longer exists. Researching the original error, one of the error descriptions was that the restore could not find the file requested.
I thought this very strange since I get the file name directly from the backupset table. Further research did indeed show that the file names were different, but unfortunately, I failed to save the details of the file names. Anyway, in looking for a new example
to show you this morning, I have found that the file names are indeed matching exactly again. If this error pops up again, I will be sure to save all details and re-post.
Thanks, regards and best wishes to you and yours, -
Error while restoring database with different name on subscriber
Hi all,
I am using merge replication in sql server 2008R2. Yesterday I wanted to create a test environment, so
I did:
1. on publisher I restored from backup production db with another name ( lets call it TEST and new files
.mdf, .ldf and no switch KEEP_REPLICATION). After this step original replication between production
dbs worked fine.
2. on subscriber I did the same: restore as new db TEST with new
files .mdf, .ldf and no switch KEEP_REPLICATION.
Unfortunately I noticed, that after second step replication stopped. SQL agent replication job on Subscriber
is gone.
Why restoring db with new name did affect original replication?
Finally the most important: replication was set up by external company and I have to bring it to live now
but I don't know this subject so good. How can I do it?
Assuming, that there is no data change on subscriber in replicated tables is it enough when I select ‘reinitialize’
on Publisher and Subscriber?
Thanks in advance
ArturHello,
Sorry for late response, but I was out of the office during last week.
Regarding problem 1: restoring replication. I contacted guy who made originally our replication and he recreated subscription agent. So this is solved.
problem 2: why did it happen?
Lydia, in link which you provided I found only info about restoring db in replication, but I didn't want to restore replication.
I checked SQL Server and Server Agent logs and there were no entries on that time. The only entries are regarding db restoring. Below:
09/11/2014 12:45:59,Backup,Unknown,Database was restored: Database: Logik_ATData_TEST<c/> creation date(time): 2012/04/27(13:55:41)<c/> first LSN: 21392:66:267<c/> last LSN: 21392:227:1<c/> number of dump devices: 1<c/> device information: (FILE=1<c/> TYPE=DISK: {'D:\MSSQLBackup\Dzienny\Logik_ATData_PROD\Logik_ATData_PROD_backup_2014_09_10_231001_6391536.bak'}). Informational message. No user action required.
09/11/2014 12:45:59,Backup,Unknown,Restore is complete on database 'Logik_ATData_TEST'. The database is now available.
09/11/2014 12:45:59,spid72,Unknown,CHECKDB for database 'Logik_ATData_TEST' finished without errors on 2012-04-26 22:50:05.490 (local time). This is an informational message only; no user action is required.
09/11/2014 12:44:53,spid72,Unknown,Recovery is writing a checkpoint in database 'Logik_ATData_TEST' (13). This is an informational message only. No user action is required.
09/11/2014 12:44:53,spid72,Unknown,Starting up database 'Logik_ATData_TEST'.
09/11/2014 12:44:51,spid72,Unknown,The database 'Logik_ATData_TEST' is marked RESTORING and is in a state that does not allow recovery to be run.
09/11/2014 12:44:51,spid72,Unknown,Starting up database 'Logik_ATData_TEST'.
In Windows application log there were also no other entries, besides these above.
I also could not check job history, because the job was gone in SSMS jobs list, while the subscription was present in SSMS Replication with info, that last successful synchronization was at 12:42 (there is a 5 min. sync period).
I also don't understand how the job was deleted, because according this manual (http://www.mssqltips.com/sqlservertip/1803/auto-alert-for-sql-agent-jobs-when-they-are-enabled-or-disabled/) I have 2 triggers in sysjobs table and every time, when
job is deleted/disabled I got @ notification. In this case I got no @.
My SQL Server version:
Product_Version Product_Level Edition
10.50.2550.0 SP1 Standard Edition (64-bit)
Any idea what happened?
Thanks,
Artur -
Restore database to azure blob failed
Hi experts,
I create a test db in SQL on Azure VM and backup to my storage account successfully. However, when I delete the database and restore using the T-SQL below, it failed. Please help.
--- query ---
USE [master]
RESTORE DATABASE [test] FROM
URL = N'https://sa1qcisapdr.blob.core.windows.net/tcd-sql2014/test_backup_2014_08_18_013128.bak'
WITH CREDENTIAL = N'AzureCredential' , FILE = 1,
MOVE N'test' TO N'https://sa1qcisapdr.blob.core.windows.net/tcd-sql2014//test.mdf',
MOVE N'test_log' TO N'https://sa1qcisapdr.blob.core.windows.net/tcd-sql2014//test_log.ldf', NOUNLOAD, STATS = 5
GO
--- result ---
Msg 3634, Level 16, State 1, Line 2
The operating system returned the error '50(The request is not supported.)' while attempting 'RestoreContainer::ValidateTargetForCreation' on 'https://sa1qcisapdr.blob.core.windows.net/tcd-sql2014//test.mdf'.
Msg 3156, Level 16, State 8, Line 2
File 'test' cannot be restored to 'https://sa1qcisapdr.blob.core.windows.net/tcd-sql2014//test.mdf'. Use WITH MOVE to identify a valid location for the file.
Msg 3634, Level 16, State 1, Line 2
The operating system returned the error '50(The request is not supported.)' while attempting 'RestoreContainer::ValidateTargetForCreation' on 'https://sa1qcisapdr.blob.core.windows.net/tcd-sql2014//test_log.ldf'.
Msg 3156, Level 16, State 8, Line 2
File 'test_log' cannot be restored to 'https://sa1qcisapdr.blob.core.windows.net/tcd-sql2014//test_log.ldf'. Use WITH MOVE to identify a valid location for the file.
Msg 3119, Level 16, State 1, Line 2
Problems were identified while planning for the RESTORE statement. Previous messages provide details.
Msg 3013, Level 16, State 1, Line 2
RESTORE DATABASE is terminating abnormally.One has to install Azure Storage Explorer and add Read/Write permissions in Shared Access Key
-
Hello everyone!
First of all, i'm sorry for posting another restore problem, but i read all threads related and i still have my problem.
I have a fresh new install of oracleXE, but when i try to restore de database from a backup store in other disk install in the same computer, using the restore database option include with the application, the program show me these steps:
STEP 1:
This operation will shut down and restore the database. Are you sure [Y/N]?
I write 'Y'.
STEP 2:
This operation will shut down and restore the database. Are you sure [Y/N]?y
Restore in progress...
El servicio solicitado ya ha sido iniciado.
Puede obtener más ayuda con el comando NET HELPMSG 2182.
Recovery Manager : Release 10.2.0.1.0 - Production on Vie Ago 31 10:20:45 2007
Copyright (c) 1982, 2005, Oracle. All rights reserved.
conectado a la base de datos destino: XE (DBID=2513092923)
RMAN> set echo on;
2> startup nomount pfile=C:\DOCUME~1\imgltda\CONFIG~1\Temp\rman_dummy.ora force;
3>
echo activado
instancia Oracle iniciada
Total del ┴rea Global del Sistema 285212672 bytes
Fixed Size 1287016 bytes
Variable Size 92277912 bytes
Database Buffers 188743680 bytes
Redo Buffers 2904064 bytes
Recovery Manager terminado.
Enter the flash recovery area location:
I write this in my flash recovery area, where i have the backup files: D:\Respaldo.
In this path i have de following folders: D:\Respaldo\XE; Inside this folder i have other folders: ARCHIVELOG, AUTOBACKUP, BACKUPSET, ONLINELOG.
STEP 3 This is my problem:
MAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: fallo del comando startup en 08/31/2007 10:24:10
RMAN-04014: fallo al iniciar: ORA-01261: Parameter db_recovery_file_dest destina
tion string cannot be translated
ORA-01263: Name given for file destination directory is invalid
OSD-04018: No se ha podido acceder al directorio o dispositivo especificado.
O/S-Error: (OS 21) El dispositivo no est┐ listo.
Recovery Manager terminado.
==================== ERROR =============================
Restore of the database failed.
RMAN Error - See log for error .
Log file is at C:\ORACLEXE\APP\ORACLE\PRODUCT\10.2.0\SERVER\DATABASE\OX
E_RESTORE.LOG.
==================== ERROR =============================
Presione una tecla para continuar . . .
The OXE_RESTORE file show me this:
Recovery Manager : Release 10.2.0.1.0 - Production on Vie Ago 31 10:23:58 2007
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Windows XP Version V5.1 Service Pack 2
CPU : 2 - type 586
Process Affinity : 0x00000000
Memory (Avail/Total): Ph:1652M/2021M, Ph+PgF:3435M/3914M, VA:2003M/2047M
Starting with debugging turned off
conectado a la base de datos destino: xe (no montada)
RMAN> set echo on;
2> restore (spfile from autobackup db_recovery_file_dest='D:\Respaldo');
3> startup nomount force;
4> restore (controlfile from autobackup);
5> alter database mount;
6> configure controlfile autobackup off;
7> restore database;
8>
echo activado
Iniciando restore en 31/08/07
se utiliza el archivo de control de la base de datos destino en lugar del catálogo de recuperación
canal asignado: ORA_DISK_1
canal ORA_DISK_1: sid=37 devtype=DISK
destino del área de recuperación: D:\Respaldo
nombre de base de datos (o nombre único de base de datos) utilizado para la búsqueda: XE
canal ORA_DISK_1: se ha encontrado una copia de seguridad automática en el área de recuperación
canal ORA_DISK_1: se ha encontrado la copia de seguridad automática: D:\RESPALDO\XE\AUTOBACKUP\2007_08_27\O1_MF_S_631711029_3F5TQOVT_.BKP
canal ORA_DISK_1: restauración de SPFILE a partir de la copia de seguridad automática terminada
restore terminado en 31/08/07
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: fallo del comando startup en 08/31/2007 10:24:10
RMAN-04014: fallo al iniciar: ORA-01261: Parameter db_recovery_file_dest destination string cannot be translated
ORA-01263: Name given for file destination directory is invalid
OSD-04018: No se ha podido acceder al directorio o dispositivo especificado.
O/S-Error: (OS 21) El dispositivo no est¿ listo.
Recovery Manager terminado.
I really do not know what is my problem and how to solve it. I hope you guys can help me. I'm under a big pressure to solve this soon.
My Operating System is: WinXP Pro
I'm using APEX 2.01
When I create the backup I use ARCHIVELOG enable
Things i try:
1. Install fresh oracle XE database, and restore
2. Install fresh oracle XE database, enable archivelog and restore
3. Install fresh oracle XE database, enable archivelog, change path of DB_RECOVERY_FILE_DEST to 'D:\Respaldo'.
4. Install fresh oracle XE database, enable archivelog, change path of DB_RECOVERY_FILE_DEST to 'D:\Respaldo', and execute: @?/sqlplus/admin/movelogs;
5. Install fresh oracle XE database, enable archivelog, change path of DB_RECOVERY_FILE_DEST to 'D:\Respaldo';, and change DB_RECOVERY_FILE_DEST_SIZE to 20G;
NOTE: sorry for my english it is not my native language. and sorry for using a spanish version of the database.
Message was edited by:
MinningWell,
After a lot of reading, i try this using rman:
SQL
1. SQL> connect xx/xx as sysdba
2. SQL> shutdown immediate
RMAN
1. RMAN> connect target XE
2. RMAN> startup nomount;
3. RMAN> restore spfile to 'C:\xe.ora' from 'D:\Respaldo\XE\AUTOBACKUP\2007_08_27\O
1_MF_S_631711029_3F5TQOVT_.BKP';
4. RMAN> alter database mount;
5. RMAN> restore database;
in point n°5 i have the following problem:
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: fallo del comando restore en 09/06/2007 16:27:09
RMAN-06026: no se han encontrado algunos destinos - abortando la restauraci¾n
RMAN-06023: no se ha encontrado ninguna copia de seguridad o copia del archivo d
e datos 4 para restaurar
RMAN-06023: no se ha encontrado ninguna copia de seguridad o copia del archivo d
e datos 3 para restaurar
RMAN-06023: no se ha encontrado ninguna copia de seguridad o copia del archivo d
e datos 2 para restaurar
RMAN-06023: no se ha encontrado ninguna copia de seguridad o copia del archivo d
e datos 1 para restaurar
I try this command to find what's going on:
RMAN> list backup;
with this result:
Lista de Juegos de Copias de Seguridad
===================
Clave BS Tipo LV Tama±o Tipo de Dispositivo Tiempo Transcurrido Hora de F
inalizaci¾n
15 Full 736.04M DISK 00:00:19 24/08/07
Clave BP: 15 Estado: EXPIRED Comprimido: NO Etiqueta: TAG20070824T12
4938
Nombre de Parte: E:\RESPALDO\XE\BACKUPSET\2007_08_24\O1_MF_NNNDF_TAG2007
0824T124938_3DY3143F_.BKP
Lista de Archivos de Datos en el juego de copias de seguridad 15
Tipo de Archivo LV SCN Pto. Ctrl. Hora de Punto de Control Nombre
1 Full 2747434 24/08/07 C:\ORACLEXE\ORADATA\XE\SYSTEM
.DBF
2 Full 2747434 24/08/07 C:\ORACLEXE\ORADATA\XE\UNDO.D
BF
3 Full 2747434 24/08/07 C:\ORACLEXE\ORADATA\XE\SYSAUX
.DBF
4 Full 2747434 24/08/07 C:\ORACLEXE\ORADATA\XE\USERS.
DBF
Clave BS Tipo LV Tama±o Tipo de Dispositivo Tiempo Transcurrido Hora de F
inalizaci¾n
16 Full 6.83M DISK 00:00:01 24/08/07
Clave BP: 16 Estado: EXPIRED Comprimido: NO Etiqueta: TAG20070824T12
5005
Nombre de Parte: E:\RESPALDO\XE\AUTOBACKUP\2007_08_24\O1_MF_S_631457405_
3DY31Y0H_.BKP
Archivo de Control Incluido: SCN de Punto de Control: 2747446 Hora de Pun
to de Control: 24/08/07
SPFILE Incluido: Hora de Modificaci¾n: 24/08/07
Clave BS Tipo LV Tama±o Tipo de Dispositivo Tiempo Transcurrido Hora de F
inalizaci¾n
17 Full 736.04M DISK 00:00:20 24/08/07
Clave BP: 17 Estado: EXPIRED Comprimido: NO Etiqueta: TAG20070824T17
0028
Nombre de Parte: E:\RESPALDO\XE\BACKUPSET\2007_08_24\O1_MF_NNNDF_TAG2007
0824T170028_3DYKQGTC_.BKP
Lista de Archivos de Datos en el juego de copias de seguridad 17
Tipo de Archivo LV SCN Pto. Ctrl. Hora de Punto de Control Nombre
1 Full 2773728 24/08/07 C:\ORACLEXE\ORADATA\XE\SYSTEM
.DBF
2 Full 2773728 24/08/07 C:\ORACLEXE\ORADATA\XE\UNDO.D
BF
3 Full 2773728 24/08/07 C:\ORACLEXE\ORADATA\XE\SYSAUX
.DBF
4 Full 2773728 24/08/07 C:\ORACLEXE\ORADATA\XE\USERS.
DBF
Clave BS Tipo LV Tama±o Tipo de Dispositivo Tiempo Transcurrido Hora de F
inalizaci¾n
18 Full 6.83M DISK 00:00:02 24/08/07
Clave BP: 18 Estado: EXPIRED Comprimido: NO Etiqueta: TAG20070824T17
0054
Nombre de Parte: E:\RESPALDO\XE\AUTOBACKUP\2007_08_24\O1_MF_S_631472454_
3DYKR7OZ_.BKP
Archivo de Control Incluido: SCN de Punto de Control: 2773741 Hora de Pun
to de Control: 24/08/07
SPFILE Incluido: Hora de Modificaci¾n: 24/08/07
Clave BS Tipo LV Tama±o Tipo de Dispositivo Tiempo Transcurrido Hora de F
inalizaci¾n
19 Full 740.95M DISK 00:00:20 27/08/07
Clave BP: 19 Estado: EXPIRED Comprimido: NO Etiqueta: TAG20070827T11
1642
Nombre de Parte: E:\RESPALDO\XE\BACKUPSET\2007_08_27\O1_MF_NNNDF_TAG2007
0827T111642_3F5TPWHN_.BKP
Lista de Archivos de Datos en el juego de copias de seguridad 19
Tipo de Archivo LV SCN Pto. Ctrl. Hora de Punto de Control Nombre
1 Full 2916556 27/08/07 C:\ORACLEXE\ORADATA\XE\SYSTEM
.DBF
2 Full 2916556 27/08/07 C:\ORACLEXE\ORADATA\XE\UNDO.D
BF
3 Full 2916556 27/08/07 C:\ORACLEXE\ORADATA\XE\SYSAUX
.DBF
4 Full 2916556 27/08/07 C:\ORACLEXE\ORADATA\XE\USERS.
DBF
Where it says 'Estado' (Status in english) I found this: 'EXPIRED', it seems that my 4 dbf files have some problem, right now i'm looking for a way to solve this, but with no luck.
I think i need a little help again... -
Import failed when Import a SBO Database in SAP Hana
Hi all,
When I try to import a SBO database Rev 69 to SAP Hana with Rev 74, I receive this error:
SAP DBTech JDBC: [2048]: column store error: table import failed: [30151] Object not found in the import directory;object=SBOCOMMON:ETL_Sen
I guess that the error not have relationship with different Revs. I imported another DB with this Rev and this work.
The import was done in 2 ways:
Script:
IMPORT DATABASE."*" FROM '<directory>' WITH REPLACE
Click right in Database, Import, select directory, select tables, import...
Does anyone know what can be or the solution??
Thanks
Best regards
Marcos TairaHello Marcos.
You could check this note.
1981315 - HANA import fails with error "not found in the import directory"
Regards.
Mario. -
Error : Restore oracle database from TSM
Hi ,
we have the RAMN backups of database in TSM.
presently that database is droped in USNODE1.
now we are trying to restore database from USSERVR23.
i am getting below error,i think its TSM error. related to hostname changes.(ANS1302E (RC2) )
http://publib.boulder.ibm.com/infocenter/tivihelp/v1r1/index.jsp?topic=/com.ibm.itsmm.doc_5.3.3/update/ANS1302E.htm
Plz suggest me
RMAN> run{
2> ALLOCATE CHANNEL c1 DEVICE TYPE sbt PARMS "ENV=(TDPO_OPTFILE=/u02/oracle/admin/tdpo.opt)";
3>
4> restore controlfile ;
5> }
allocated channel: c1
channel c1: sid=1641 devtype=SBT_TAPE
channel c1: Tivoli Data Protection for Oracle: version 5.2.0.0
Starting restore at 29-MAY-09
channel c1: starting datafile backupset restore
channel c1: restoring control file
channel c1: reading from backup piece HOT1-20090424_1600-5fkd9nr6_1_1
ORA-19870: error reading backup piece HOT1-20090424_1600-5fkd9nr6_1_1
ORA-19507: failed to retrieve sequential file, handle="HOT1-20090424_1600-5fkd9nr6_1_1", parms=""
ORA-27029: skgfrtrv: sbtrestore returned error
ORA-19511: Error received from media manager layer, error text:
ANS1302E (RC2) No objects on server match query
failover to previous backup
Thanks,
VIJMay I ask a couple of questions?
Is the original backup from a RAC instance?
Are you using a Catalog for backup/restore?
What happens if you just use the control file backup, can the restore find the file?
See my question posted in this forum RMAN RAC and TSM features
Robert -
Privilege errors after database import
Hi,
I just built an database server with window 2003, oracle 10.1.0.4 with 10.1.0.2 version of oracle workspace manager. I imported my database (with the same DB versions) however I'm not able to execute the dbms_wm commands. My test user has the wm_admin_role and is able to enable and disable versioning however, I can not create a workspace. I get the following error when I attempt to run dbms_wm.GrantSystemPriv logged in as any DBA user with wm_admin_role:
ora-20076: insufficient privileges to grant priv_ANY_WORKSPACE
ora-06512: at "SYS.LTPRIV"
ora-06512: at "SYS.LTPRIV"
ora-06512: at "SYS.LT"
I am able to select dbms_wm.getworkspace from dual and 'LIVE' workspace is returned. However, if I attempt to run dbms_wm.gotoworkspace('LIVE') it returns
ora-20122: workspace 'LIVE' does not exist
Any info is greatly appreciated...
TCTUnfortunately this is NOT the solution. The sys.portal_login only works for the current sql-session. As soon as you login for a second time, you have to execute this procedure again. So, the upgrade to 309 is still not possible.
According to TAR 2063294.55 Oracle will NOT support full database exports/imports for backing up Portal environments. They only accept the Portal import/export-utilities (which are unreliable and unworkable) and database-filebackups (which are not possible if you want to restore only one schema).
So, my Portal-308-environment is working now, but it can never be upgraded to 309.
Or does anyone else has an option? -
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 -
Failed to mount database "General Users". Error: An Active Manager operation failed
Failed to mount database "General Users". Error: An Active Manager operation failed. Error: The database action failed. Error: Database 'General Users' on server 'EX02' cannot be mounted due to a previous error: At '12/3/2014
3:52:17 PM' the Exchange store database 'General Users' copy on this server appears to be inconsistent with the active database copy or is corrupted. For more details about the failure, consult the Event log on the server for other storage and "ExchangeStoreDb"
events. A successful failover restored service. If you have addressed the underlying problem, or if you have decided to attempt to mount the database despite this error, the mount operation may be attempted by using the '-Force' parameter of the Mount-Database
cmdlet. [Database: General Users, Server: EX02.domain.com]
Md. Ramin HossainHi,
From your description, it is recommended to suspend the failed database copy at first using the cmdlet below.
Suspend-MailboxDatabaseCopy -Identity "xxx"
And then reseed the database with a new copy using Update-MailboxDatabaseCopy -Identity "xxx" -DeleteExistingFiles cmdlet.
What's more, here is a helpful thread for your reference.
Update-MailboxDatabaseCopy
http://technet.microsoft.com/en-us/library/dd335201(v=exchg.150).aspx
Hope this can be helpful to you.
Best regards,
Amy Wang
TechNet Community Support -
Hello,
I was trying to restore a database but it says failed, very backup data says verified but the restoration fails, tried also by using the following query
restore filelistonly
from disk = 'D:\GrantApp.bak'
go
restore database GrantApp
from disk = 'D:\GrantApp.bak'
with move 'GrantApp' to 'C:\Program Files\Microsoft SQL Server\MSSQL11.SQLEXPRESS\MSSQL\DATA\GrantApp.mdf',
move 'GrantApp_log' to 'C:\Program Files\Microsoft SQL Server\MSSQL11.SQLEXPRESS\MSSQL\DATA\GrantApp_log.ldf'
but this gives me error as
(2 row(s) affected)
Msg 3634, Level 16, State 1, Line 1
The operating system returned the error '5(Access is denied.)' while attempting 'RestoreContainer::ValidateTargetForCreation' on 'C:\Program Files\Microsoft SQL Server\MSSQL11.SQLEXPRESS\MSSQL\DATA\GrantApp.mdf'.
Msg 3156, Level 16, State 5, Line 1
File 'GrantApp' cannot be restored to 'C:\Program Files\Microsoft SQL Server\MSSQL11.SQLEXPRESS\MSSQL\DATA\GrantApp.mdf'. Use WITH MOVE to identify a valid location for the file.
Msg 3634, Level 16, State 1, Line 1
The operating system returned the error '5(Access is denied.)' while attempting 'RestoreContainer::ValidateTargetForCreation' on 'C:\Program Files\Microsoft SQL Server\MSSQL11.SQLEXPRESS\MSSQL\DATA\GrantApp_log.ldf'.
Msg 3156, Level 16, State 5, Line 1
File 'GrantApp_log' cannot be restored to 'C:\Program Files\Microsoft SQL Server\MSSQL11.SQLEXPRESS\MSSQL\DATA\GrantApp_log.ldf'. Use WITH MOVE to identify a valid location for the file.
Msg 3119, Level 16, State 1, Line 1
Problems were identified while planning for the RESTORE statement. Previous messages provide details.
Msg 3013, Level 16, State 1, Line 1
RESTORE DATABASE is terminating abnormally.Did you try restoring to the same path but with different MDF and LDF names? What was the outcome?
Does the database currently exist and thus you are trying to overwrite it?
Can you create a new database in the same folder using syntax similar to this:
CREATE
DATABASE[test]
ON
PRIMARY
NAME=N'test',FILENAME=N'C:\Program
Files\Microsoft SQL Server\MSSQL11.SQLEXPRESS\MSSQL\DATA\test.mdf',SIZE=4096KB,MAXSIZE=UNLIMITED,FILEGROWTH=1024KB)
LOG
ON
NAME=N'test_log',FILENAME=N'C:\Program
Files\Microsoft SQL Server\MSSQL11.SQLEXPRESS\MSSQL\DATA\test_log.ldf',SIZE=1024KB,MAXSIZE=2048GB,FILEGROWTH=10%)
GO
Maybe you are looking for
-
Can i take RAM out of my old iMac (2008) and put it in my new iMac(2011)?
I added 2GB of RAM to my 2008 iMac. Can I add this to my new iMac (2011)? It came with 4GB of RAM.
-
Balance Sheet Items- Input Schedule
Hi Guys, I have a input schedule which have Assets Items. I enter some figure in it and send the data. It says data sent successfully. but I dont see any data in the schedule. Though I can see the data from BI side, but data is not visible in the inp
-
Volume down button not responding?
Volume down button not working however able to reduce volume by swiping screen.
-
Hi Guys: this morning, someing wierd started happening. Whenever I double click a transition, and it apears any transition, FCP quits suddenly. I can add the trans from either the effects tab or the effects menu; fine. But if I doule click, so I can
-
How to set EOF as delimiter in Format Builder?
I'm triying to establish the last item delimiter of a one line/record file whitch has nothing but EOF, I mean that this item ends whithout delimiter, only the file ends. How do I set an EOF as delimiter? Thanks!