With Samsung Galaxy, and possibly other devices, phones and tablets, if your date and time are off by more than a few hours, you won’t be able access the internet even though you’re able to connect to the wifi. Before you reset your device back to factory settings, check the time and date!
No, the numbers don’t work anymore 🙁
|Draconian Information Systems
“Wisdom? What’s the difference between that and Intelligence?”
“What?” She flinched as the others glared as though in chorus. “What?” she whispered.
“I said, ‘Edith Bunker’—from All in the family? Not too bright, but wise as all hell. Or to take a counterexample, Richard Nixon. Get it?”
Oracle will require you to configure the Oracle RDBMS to use operating system authentication but if you inherit an Oracle instance, you will want to disable os authentication when possible. When the OS_AUTHENT_PREFIX is set, any os user that is created with “IDENTIFIED EXTERNALLY” will have the prefix. For example, in the below example, the value is “ops$”. The os user johnnybgood will have an internal Oracle user id of “ops$johnnybgood”. It’s a handy way to quickly identify such users but it isn’t full proof.
show parameter OS_AUTHENT_PREFIX
lang-NAME TYPE VALUE ------------------------------------ ----------- ------------------------------ os_authent_prefix string ops$
To determine exactly which users are set up for os authentication run the following query:
set pagesize 5000 set linesize 999 set trimspool on select gn.GLOBAL_NAME as "Instance", username, authentication_type from dba_users du, global_name gn where authentication_type = 'EXTERNAL'
Now, there are valid reasons to use os authentication but I would push LDAP long before os authentication.
From the Oracle Security Admin Guide:
Advantages of External Authentication
Following are the advantages of external authentication:
More choices of authentication mechanism are available, such as smart cards, fingerprints, Kerberos, or the operating system.
Many network authentication services, such as Kerberos support single sign-on, enabling users to have fewer passwords to remember.
If you are already using some external mechanism for authentication, such as one of those listed earlier, then there may be less administrative overhead to use that mechanism with the database as well.
00:0006:00000:00001:2014/01/08 09:03:09.09 server ERROR: Can't get a new log page in db 4. num_left=17 num_in_plc=17. 00:0006:00000:00001:2014/01/08 09:03:09.09 server Error: 1105, Severity: 17, State: 7 00:0006:00000:00001:2014/01/08 09:03:09.09 server Can't allocate space for object 'syslogs' in database 'mydb' because 'logsegment' segment is full/has no free extents. If you ran out of space in syslo gs, dump the transaction log. Otherwise, use ALTER DATABASE to increase the size of the segment. 00:0006:00000:00001:2014/01/08 09:03:09.09 server Error: 3475, Severity: 21, State: 7 00:0006:00000:00001:2014/01/08 09:03:09.09 server There is no space available in SYSLOGS to log a record for which space has been reserved in database 'mydb' (id 4). This process will retry at interval s of one minute.
So what to do? If you separate your data and log segments, you will need to temporarily add the log segment to a data device so the database can recover. Once it recovers, we can add space to the log and remove the log segment from the data device. For good measure, we run dbccs to correct any allocation issues that may be contributing to the out of log space.
Add the log segment to a data device (use sp_helpdb dbname to determine which data device has space):
exec sp_configure "allow updates", 1 go update sysusages set segmap = 7 where dbid = 4 and lstart = 1492992 go checkpoint go shutdown with nowait go
Add space to the log:
alter database mydb log on mydevicel001 = 500 go
Before we do anything else, let’s run dbccs. Of course, you will want to run the dbccs without the fix option to identify if there are other issues prior to running with the fix:
exec kill_user_connections mydb exec kill_user_connections mydb exec kill_user_connections mydb exec kill_user_connections mydb exec kill_user_connections mydb exec sp_dboption mydb, 'dbo use', true exec sp_dboption mydb, 'single user', true dbcc traceon(3604) dbcc checkdb(mydb, fix_spacebits) dbcc checkalloc(mydb, fix) exec sp_dboption mydb, 'dbo use', false exec sp_dboption mydb, 'single user', false go
If no lingering issues, we can remove the log segment from the data device:
exec sp_dboption mydb, 'single user', true go use mydb go exec sp_dropsegment logsegment, mydb, mydeviced005 go use master go exec sp_dboption mydb, 'single user', false go
SAP is fixing Bug CR 756957 in ASE 15.7 SP110 that may be the root cause of the 3475 error:
In certain circumstances, databases, including system databases, can incorrectly get into LOG SUSPEND mode, issuing message: “Space available in the log segment has fallen critically low in database ‘ < dbname > ‘. All future modifications to this database will be suspended until the log is successfully dumped and space becomes available.” This may happen even though there is much unreserved space in the database. The problem may also manifest in 3475 errors: “There is no space available in SYSLOGS to log a record for which space has been reserved in database < dbname > .”