Closes the current error log file and cycles the error log extension
numbers just like a server restart. The new error log contains version
and copyright information and a line indicating that the new log has
been created.
Every time SQL Server is started, the current error log is renamed to errorlog.1; errorlog.1 becomes errorlog.2, errorlog.2 becomes errorlog.3, and so on. sp_cycle_errorlog enables you to cycle the error log files without stopping and starting the server.
http://technet.microsoft.com/en-us/library/ms182512%28v=sql.100%29.aspx
Set up a friendly environment to share my understanding and ideas about Oracle / Oracle Spatial database administration, ESRI ArcSDE Geodatabase administration and UNIX (Solaris) operating system.
Friday, September 27, 2013
Thursday, September 26, 2013
Understanding "login failed" (Error 18456) error messages in SQL Server 2005
Got login errors in the SQL Server 2005 databases. The following link solves the issue.
If the server encounters an error that prevents a login from succeeding, the client will display the following error mesage.
Msg 18456, Level 14, State 1, Server, Line 1
Login failed for user ''
Note that the message is kept fairly nondescript to prevent information disclosure to unauthenticated clients. In particular, the 'State' will always be shown to be '1' regardless of the nature of the problem. To determine the true reason for the failure, the administrator can look in the server's error log where a corresponding entry will be written. An example of an entry is:
Understanding "login failed" (Error 18456) error messages in SQL Server 2005
If the server encounters an error that prevents a login from succeeding, the client will display the following error mesage.
Msg 18456, Level 14, State 1, Server
Login failed for user '
Note that the message is kept fairly nondescript to prevent information disclosure to unauthenticated clients. In particular, the 'State' will always be shown to be '1' regardless of the nature of the problem. To determine the true reason for the failure, the administrator can look in the server's error log where a corresponding entry will be written. An example of an entry is:
2006-02-27 00:02:00.34 Logon Error: 18456, Severity: 14, State: 8.
2006-02-27 00:02:00.34 Logon Login failed for user ''. [CLIENT:
n
The
key to the message is the 'State' which the server will accurately set
to reflect the source of the problem. In the example above, State 8
indicates that the authentication failed because the user provided an
incorrect password. The common error states and their descriptions are
provided in the following table:
|
ERROR STATE
|
ERROR DESCRIPTION
|
|
2 and 5
|
Invalid userid
|
|
6
|
Attempt to use a Windows login name with SQL Authentication
|
|
7
|
Login disabled and password mismatch
|
|
8
|
Password mismatch
|
|
9
|
Invalid password
|
|
11 and 12
|
Valid login but server access failure
|
|
13
|
SQL Server service paused
|
|
18
|
Change password required
|
Tuesday, June 25, 2013
ArcSDE Operating system authentication
Operating system authentication | |
| Release 9.3 | |
Using Windows-authenticated users or groups in SQL Server | |
| Release 9.3 | |
Wednesday, June 19, 2013
SQL Server Catalog Views
Link: http://msdn.microsoft.com/en-us/library/ms174365.aspx
The catalog views in SQL Server have been organized into the following categories:
Monday, June 10, 2013
ORA-16038 ORA-19809 ORA-00312
Got the error when starting an Oracle database:
SQL> startup
ORACLE instance started.
Total System Global Area 1010827264 bytes
Fixed Size 2045480 bytes
Variable Size 385878488 bytes
Database Buffers 603979776 bytes
Redo Buffers 18923520 bytes
Database mounted.
ORA-16038: log 3 sequence# 42 cannot be archived
ORA-19809: limit exceeded for recovery files
ORA-00312: online log 3 thread 1: '/u02/oradata/DB/redo03.log'
SQL> startup
ORACLE instance started.
Total System Global Area 1010827264 bytes
Fixed Size 2045480 bytes
Variable Size 385878488 bytes
Database Buffers 603979776 bytes
Redo Buffers 18923520 bytes
Database mounted.
ORA-16038: log 3 sequence# 42 cannot be archived
ORA-19809: limit exceeded for recovery files
ORA-00312: online log 3 thread 1: '/u02/oradata/DB/redo03.log'
Solution:
To solve ORA-19809 error, increase the value of db_recovery_file_dest_size parameter. And start the database:
SQL> ALTER SYSTEM SET DB_RECOVERY_FILE_DEST_SIZE=3G SCOPE=BOTH;
SQL> shutdown abort
SQL> startup