I encountered a serious problem today. As I was trying to map a drive of another server (win2k3 server) from my windows 2008 server, I encountered a weird error. I entered in my command line,
net use q: \\<ip>\g$ /User:<user> <pass>
But it returned, "The specified network password is not correct". I was sure that my password is correct. I tried mapping the drive in reverse from 2k3 to 2k8 and it worked. This sure smells a problem with local policy.
I searched the net for solutions and found out that my hunch was correct.
The solution I tried are as follows.
1) Click Start > Run then type secpol.msc on the box
2) Local Policies > Security Options. On the List on the side, find Network Security: LAN Manager Authentication and right click properties.
3) On the dop-down, select Send LM & NTLM - use NTLMv2 session security if negotiated.
This solution solved my problem and I hope this helps.
Source:
ServerFault Forums
Friday, July 1, 2011
Wednesday, June 29, 2011
Deleted offline db undo tablespace
Sometime last week, I encountered a problem concerning by offline backup.
My offline backup comprises of all datafiles and controlfiles copied to another disk when the whole db was offline hence the term. I even saved the trace file from the original to recreate controlfile if something happens. (using alter database backup controlfile to trace)
I used the setup to easily return back the database when something needs to be rolled back to a previous state. I accidentally deleted the backup for the undo tablespace instead of the db I am working on. Here's the solution that worked in my case.
1. on the pfile, change the undo_management=manual (on my case it is set to auto so I change it) then recreate spfile using that pfile
create spfile from pfile='<path/file .ora>'
2. start the database using startup nomount
3. Recreate the controlfile based on the trace file but remove the entry regarding the undo tablespace path/file.
CREATE CONTROLFILE REUSE DATABASE ( <and other paramaters just check on the trace file>)
DATAFILE
(<datafiles of the database>)
'M:\ORACLE\ORADATA\ABUYER81\UNDOTBS01.DBF', >>> remove this line
CHARACTER SET UTF8;
4. execute recover database
5. open the database using alter database open;
6. recreate the undo tablespace
create undo tablespace <undotbs name> datafile '<path/file .dbf>'
size 100m autoextend on maxsize unlimited; <<<this depends on the settings you'll be using
7. revert back to undo_management=auto on the pfile. shutdown, recreate spfile then start the database again.
Source:
I based this solution How to handle lost undo datafile
My offline backup comprises of all datafiles and controlfiles copied to another disk when the whole db was offline hence the term. I even saved the trace file from the original to recreate controlfile if something happens. (using alter database backup controlfile to trace)
I used the setup to easily return back the database when something needs to be rolled back to a previous state. I accidentally deleted the backup for the undo tablespace instead of the db I am working on. Here's the solution that worked in my case.
1. on the pfile, change the undo_management=manual (on my case it is set to auto so I change it) then recreate spfile using that pfile
create spfile from pfile='<path/file .ora>'
2. start the database using startup nomount
3. Recreate the controlfile based on the trace file but remove the entry regarding the undo tablespace path/file.
CREATE CONTROLFILE REUSE DATABASE ( <and other paramaters just check on the trace file>)
DATAFILE
(<datafiles of the database>)
'M:\ORACLE\ORADATA\ABUYER81\UNDOTBS01.DBF', >>> remove this line
CHARACTER SET UTF8;
4. execute recover database
5. open the database using alter database open;
6. recreate the undo tablespace
create undo tablespace <undotbs name> datafile '<path/file .dbf>'
size 100m autoextend on maxsize unlimited; <<<this depends on the settings you'll be using
7. revert back to undo_management=auto on the pfile. shutdown, recreate spfile then start the database again.
Source:
I based this solution How to handle lost undo datafile
Monday, May 23, 2011
Server Memory Installation
We have installed memory modules on a blade server. The problem arises when the server does not detect the newly installed memory modules
Analysis: Upon looking for restriction by Operating System. It seems that the server wasn't detecting within the limits. Since the OS is Win2k Advanced Server, the System must be able to detect up to 8gb worth of RAM. The system only detects 4gb of RAM
Solution. Include /AWE and /PAE at the end of the last parameter
Source: There is a greater explanation of the two parameter on a separate site found here.
Analysis: Upon looking for restriction by Operating System. It seems that the server wasn't detecting within the limits. Since the OS is Win2k Advanced Server, the System must be able to detect up to 8gb worth of RAM. The system only detects 4gb of RAM
Solution. Include /AWE and /PAE at the end of the last parameter
Source: There is a greater explanation of the two parameter on a separate site found here.
Wednesday, May 18, 2011
Uninstallation Problem
I am having a hard time uninstalling a program. It presents me an error:
"Windows Installer Service could not be accessed"
OS: Windows Server 2000
Analysis and Steps Taken: On the error message, I tried restarting the service for Windows Installer but it does not resolve the problem. I also tried stopping the service of the program but sadly, it does not respond. My last resort was looking for solutions on the net. Most of the solution presented on the internet requires editing the registry. I have tried editing the registry but one mistake would be catastrophic so I opted to trying other solutions. The first solution I have encountered involves re-registering the Windows Installer. Details of the solution are indicated here (method one). Nothing happened on my situation. I also tried the permission solution indicated on the same site but it didnt solve anything. I continue look for solution and I end up another solution specific to my problem which involves inability to add or remove a program.
Solution: I ended up reinstalling the Windows Installer 3.1 based on the steps given on Microsoft KB-315346 Method 2. I followed every detail indicated in the article and voila! I uninstalled the program without the error.
Site Source: http://support.microsoft.com/kb/315346
"Windows Installer Service could not be accessed"
OS: Windows Server 2000
Analysis and Steps Taken: On the error message, I tried restarting the service for Windows Installer but it does not resolve the problem. I also tried stopping the service of the program but sadly, it does not respond. My last resort was looking for solutions on the net. Most of the solution presented on the internet requires editing the registry. I have tried editing the registry but one mistake would be catastrophic so I opted to trying other solutions. The first solution I have encountered involves re-registering the Windows Installer. Details of the solution are indicated here (method one). Nothing happened on my situation. I also tried the permission solution indicated on the same site but it didnt solve anything. I continue look for solution and I end up another solution specific to my problem which involves inability to add or remove a program.
Solution: I ended up reinstalling the Windows Installer 3.1 based on the steps given on Microsoft KB-315346 Method 2. I followed every detail indicated in the article and voila! I uninstalled the program without the error.
Site Source: http://support.microsoft.com/kb/315346
Subscribe to:
Posts (Atom)