Friday, January 22, 2016
Oracle Installation Issue Please ensure that this directory is writable and has at least 45MB of disk space
Virus
AntiVirus
Rights
Space in temp
Cross verify the registry using 'regedit' and check it doesn't have any unclean services of previos oracle installation (if any).
a) Insufficient free space in the temporary directory.
b) Insufficient access rights on the temporary directory.
c) Not using a local console.
d) Corrupted software set.
e) Wrong Unzip utility is used.
For Database: %Oracle_extracted_media%\database\install\oraparam.ini
Edit value: BOOTSTRAP=TRUE
New value: BOOTSTRAP=FALSE << this allows OUI creates less files /tmp and avoids creation of autorun.inf file @ %tmp%
2) Then run the setup.exe -debug from the media (where the file praparam.ini edited ).
Example: run setup.exe -debug from required media location
cd %Oracle_extracted_media%\database\setup.exe
create autorun.inf file in temp folder, try to save this
unload officescan
PLS-00920 parameter plsql_native_library_dir is not set
sho parameter plsql
plsql_code_type string INTERPRETED
plsql_compiler_flags string INTERPRETED, NON_DEBUG
10g
alter system set plsql_code_type ='INTERPRETED';
plsql_code_type string INTERPRETED
plsql_compiler_flags string INTERPRETED, NON_DEBUG
10g
alter system set plsql_code_type ='INTERPRETED';
The specified DSN contains an architecture mismatch between the Driver and Application
64 bit m/c
Reason
odbc at both location
c:\windows\system32\odbcad32.exe
c:\windows\sysWOW64\odbcad32.exe
remove odbc connection from c:\windows\system32\odbcad32.exe
You will get this error if you attempt to do the following on a 64-bit Windows machine:
Connect a 64-bit application to a data source for a 32-bit ODBC driver.
Connect a 32-bit application to a data source for a 64-bit ODBC driver.
If you are using a 64-bit application, it will be linked against the 64-bit version of the Microsoft ODBC Driver Manager, which can only load a 64-bit ODBC driver. You can only connect to data sources for ODBC drivers that are listed in the 64-bit ODBC Data Source Administrator (accessible from Administrative tools in Control Panel).
Similarly, if you are using a 32-bit application, it will be linked against the 32-bit version of the Microsoft ODBC Driver Manager, which can only load a 32-bit ODBC driver. You can only connect to data sources for ODBC drivers that are listed in the 32-bit ODBC Data Source Administrator (accessible by running %windir%\syswow64\odbcad32.exe in the Windows Run dialog box).
If an ODBC driver is listed in both versions of the ODBC Data Source Administrator, both a 32-bit and a 64-bit version of that driver are installed.
Reason
odbc at both location
c:\windows\system32\odbcad32.exe
c:\windows\sysWOW64\odbcad32.exe
remove odbc connection from c:\windows\system32\odbcad32.exe
You will get this error if you attempt to do the following on a 64-bit Windows machine:
Connect a 64-bit application to a data source for a 32-bit ODBC driver.
Connect a 32-bit application to a data source for a 64-bit ODBC driver.
If you are using a 64-bit application, it will be linked against the 64-bit version of the Microsoft ODBC Driver Manager, which can only load a 64-bit ODBC driver. You can only connect to data sources for ODBC drivers that are listed in the 64-bit ODBC Data Source Administrator (accessible from Administrative tools in Control Panel).
Similarly, if you are using a 32-bit application, it will be linked against the 32-bit version of the Microsoft ODBC Driver Manager, which can only load a 32-bit ODBC driver. You can only connect to data sources for ODBC drivers that are listed in the 32-bit ODBC Data Source Administrator (accessible by running %windir%\syswow64\odbcad32.exe in the Windows Run dialog box).
If an ODBC driver is listed in both versions of the ODBC Data Source Administrator, both a 32-bit and a 64-bit version of that driver are installed.
ORA-00344 unable to re-create online log ORA-27040 file create error unable to create file
http://blog.dbvisit.com/activating-standby-database-failover/
ORA-00344 unable to re-create online log ORA-27040 file create error unable to create file
SQL> alter database rename file '/oracle/oradata/dbvisitp/redo01.log'
to '/oracleX/oradata/dbvisitp/redo01.log';
Database altered.
SQL> alter database activate standby database;
alter database activate standby database
*
ERROR at line 1:
ORA-00344: unable to re-create online log
'/oracleX/oradata/dbvisitp/redo01.log'
ORA-27040: file create error, unable to create file
Linux Error: 2: No such file or directory
The database is still a standby database as the activation failed.
We cannot manually create the redo logs, as this is an Oracle internal operation.
The only thing we can do is to give the correct location for the redo log files.
Rename the redo log to the correct location:
SQL> alter database rename file '/oracleX/oradata/dbvisitp/redo01.log' to
'/oracle/oradata/dbvisitp/redo01.log';
Database altered.
SQL> alter database activate standby database;
Database altered.
SQL>
Note: all previous backups of this database are now invalid and cannot be used to restore this database. This is because of the RESETLOGS command which resets the archive sequence number (SEQUENCE#) and invalidates all previous archive logs. The SCN number of the database is not reset.
ORA-00344 unable to re-create online log ORA-27040 file create error unable to create file
SQL> alter database rename file '/oracle/oradata/dbvisitp/redo01.log'
to '/oracleX/oradata/dbvisitp/redo01.log';
Database altered.
SQL> alter database activate standby database;
alter database activate standby database
*
ERROR at line 1:
ORA-00344: unable to re-create online log
'/oracleX/oradata/dbvisitp/redo01.log'
ORA-27040: file create error, unable to create file
Linux Error: 2: No such file or directory
The database is still a standby database as the activation failed.
We cannot manually create the redo logs, as this is an Oracle internal operation.
The only thing we can do is to give the correct location for the redo log files.
Rename the redo log to the correct location:
SQL> alter database rename file '/oracleX/oradata/dbvisitp/redo01.log' to
'/oracle/oradata/dbvisitp/redo01.log';
Database altered.
SQL> alter database activate standby database;
Database altered.
SQL>
Note: all previous backups of this database are now invalid and cannot be used to restore this database. This is because of the RESETLOGS command which resets the archive sequence number (SEQUENCE#) and invalidates all previous archive logs. The SCN number of the database is not reset.
Could not load file or assembly 'ChilkatDotNet4' or one of its dependencies. An attempt was made to load a program with an incorrect format.
Common Error #1
The Chilkat .NET assembly is a mixed-mode assembly. It provides a managed API, but the inner core contains native code. A process must load the correct assembly at runtime. A 32-bit process must load the 32-bit ChilkatDotNet4.dll, and a 64-bit process must load the 64-bit ChilkatDotNet4.dll. When a process tries to load the incorrect format, the following error will occur:
Could not load file or assembly 'ChilkatDotNet4' or one of its dependencies. An attempt was made to load a program with an incorrect format.
See Incorrect Format for more information.
check application pool (32 bit enable or not)
check ChilkatDotNet4 version 9.3.1
Microsoft Visual C++ 2010 SP1 Redistributable 32 bit / 64 bit
Microsoft Visual C++ 2012 SP1 Redistributable 32 bit/ 64 bit
The Chilkat .NET assembly is a mixed-mode assembly. It provides a managed API, but the inner core contains native code. A process must load the correct assembly at runtime. A 32-bit process must load the 32-bit ChilkatDotNet4.dll, and a 64-bit process must load the 64-bit ChilkatDotNet4.dll. When a process tries to load the incorrect format, the following error will occur:
Could not load file or assembly 'ChilkatDotNet4' or one of its dependencies. An attempt was made to load a program with an incorrect format.
See Incorrect Format for more information.
check application pool (32 bit enable or not)
check ChilkatDotNet4 version 9.3.1
Microsoft Visual C++ 2010 SP1 Redistributable 32 bit / 64 bit
Microsoft Visual C++ 2012 SP1 Redistributable 32 bit/ 64 bit
Could not load file or assembly 'ChilkatDotNet4.dll' or one of its dependencies. The specified module could not be found.
install
vcredist_x64
vcredist_x86
vcredist_x64_2010
vcredist_x86_2010
vcredist_x64_2012
vcredist_x86_2012
Common Error #2
The Chilkat .NET assembly requires the VC++ runtime to be installed on any computer where your application runs. Most computers will already have it installed. Your development computer will have it because Visual Studio has been installed. However, if deploying to a computer where the VC++ runtime is not available, the following error will occur:
Could not load file or assembly 'ChilkatDotNet4.dll' or one of its dependencies. The specified module could not be found.
http://www.microsoft.com/en-us/download/details.aspx?id=5555
Common Error #1
The Chilkat .NET assembly is a mixed-mode assembly. It provides a managed API, but the inner core contains native code. A process must load the correct assembly at runtime. A 32-bit process must load the 32-bit ChilkatDotNet4.dll, and a 64-bit process must load the 64-bit ChilkatDotNet4.dll. When a process tries to load the incorrect format, the following error will occur:
Could not load file or assembly 'ChilkatDotNet4' or one of its dependencies. An attempt was made to load a program with an incorrect format.
See Incorrect Format for more information.
vcredist_x64
vcredist_x86
vcredist_x64_2010
vcredist_x86_2010
vcredist_x64_2012
vcredist_x86_2012
Common Error #2
The Chilkat .NET assembly requires the VC++ runtime to be installed on any computer where your application runs. Most computers will already have it installed. Your development computer will have it because Visual Studio has been installed. However, if deploying to a computer where the VC++ runtime is not available, the following error will occur:
Could not load file or assembly 'ChilkatDotNet4.dll' or one of its dependencies. The specified module could not be found.
http://www.microsoft.com/en-us/download/details.aspx?id=5555
Common Error #1
The Chilkat .NET assembly is a mixed-mode assembly. It provides a managed API, but the inner core contains native code. A process must load the correct assembly at runtime. A 32-bit process must load the 32-bit ChilkatDotNet4.dll, and a 64-bit process must load the 64-bit ChilkatDotNet4.dll. When a process tries to load the incorrect format, the following error will occur:
Could not load file or assembly 'ChilkatDotNet4' or one of its dependencies. An attempt was made to load a program with an incorrect format.
See Incorrect Format for more information.
PLS-00123 program too large (Diana nodes)
in 10g, plsql is not taking such size.
better way to use large procedures and functions should always be defined within packages
microsoft excel cannot open or save any more documents because there is not enough available memory
at Control Panel \ All Control Panel Items \ Default Programs \ Set Default Programs \ Set Program Associations
In Excel, go to File/Options/Trust Center/Trust Center Settings/Protected View. Untick the "Enable Protected View for Outlook Attachments" - and all will be well.
Labels:
Windows System Admin
no mapping between account name and security ids was done server 2008 service installation
grant rights of folder
If you do choose the SYSPREP route though here is what you need to do:
From the Start Menu select Run
Enter C:\Windows\System32\sysprep\sysprep.exe in the box and click OK
Be sure that Enter System Out-of-Box Experience (OOBE) is selected
Check the box next to Generalize (If this is not select the SID won’t get changed)
Click OK and follow the prompts when the system reboots.
C:\Windows\System32\sysprep\sysprep.exe
If you do choose the SYSPREP route though here is what you need to do:
From the Start Menu select Run
Enter C:\Windows\System32\sysprep\sysprep.exe in the box and click OK
Be sure that Enter System Out-of-Box Experience (OOBE) is selected
Check the box next to Generalize (If this is not select the SID won’t get changed)
Click OK and follow the prompts when the system reboots.
C:\Windows\System32\sysprep\sysprep.exe
Labels:
Windows System Admin
Silverlight out of browser export to excel download issue require Administrator to create the file
at time of package build, in properties there is a tick for out of browser
LD Ledger Client Code not search
Insert into tblsaudatable select distinct Firmnumber,Oowncode,'C','N' from sauda minus
Select distinct cFirmnumber,cclientcode,'C','N' from tblsaudatable Where cSegment='C' ;
Insert into Tblsaudascriptable select distinct Firmnumber,Oowncode,Compcode,'C' from sauda minus
Select distinct cFirmnumber,Cclientcode,cscripcode,'C' from Tblsaudascriptable Where cSegment='C' ;
Insert into tblsaudatable select distinct Firmnumber,Oowncode,'D','N' from fosauda minus
Select distinct cFirmnumber,CClientcode,'D','N' from tblsaudatable Where cSegment='D' ;
Insert into Tblsaudascriptable select distinct Firmnumber,Oowncode,Compcode,'D' from fosauda minus
Select distinct cFirmnumber,Cclientcode,Cscripcode,'D' from Tblsaudascriptable Where cSegment='D' ;
Insert into Tblfintable select distinct firmnumber,oowncode,branchcode,'N' from ledger minus
select distinct cfirmnumber,Cclientcode,Cbranchcode,'N' from Tblfintable ;
Select distinct cFirmnumber,cclientcode,'C','N' from tblsaudatable Where cSegment='C' ;
Insert into Tblsaudascriptable select distinct Firmnumber,Oowncode,Compcode,'C' from sauda minus
Select distinct cFirmnumber,Cclientcode,cscripcode,'C' from Tblsaudascriptable Where cSegment='C' ;
Insert into tblsaudatable select distinct Firmnumber,Oowncode,'D','N' from fosauda minus
Select distinct cFirmnumber,CClientcode,'D','N' from tblsaudatable Where cSegment='D' ;
Insert into Tblsaudascriptable select distinct Firmnumber,Oowncode,Compcode,'D' from fosauda minus
Select distinct cFirmnumber,Cclientcode,Cscripcode,'D' from Tblsaudascriptable Where cSegment='D' ;
Insert into Tblfintable select distinct firmnumber,oowncode,branchcode,'N' from ledger minus
select distinct cfirmnumber,Cclientcode,Cbranchcode,'N' from Tblfintable ;
ORA-29861 domain index is marked LOADINGFAILEDUNUSABLE
Exec dbms_network_acl_admin.create_acl ('utl_http_access.xml','Normal Access','DPCDSL',TRUE,'connect',NULL,NULL);
Exec dbms_network_acl_admin.add_privilege (acl => 'utl_http_access.xml', principal => 'DPCDSL',is_grant => TRUE, privilege => 'resolve');
Exec dbms_network_acl_admin.assign_acl ('utl_http_access.xml', '*',NULL,NULL);
Commit ;
ERROR at line 1:
ORA-29861: domain index is marked LOADING/FAILED/UNUSABLE
ORA-06512: at "SYS.DBMS_NETWORK_ACL_ADMIN", line 252
ORA-06512: at line 1
select owner,index_name from all_indexes where domidx_status != 'VALID' or domidx_opstatus !='VALID';
alter index xdb.XDB$ACL_XIDX rebuild;
"ORA-28547: Connection to Server Failed, Probable Oracle Net Admin Error"
Edit the SQLNET.ora file in a text editor such as Notepad.
Change this line to what is shown below:
#SQLNET.AUTHENTICATION_SERVICES = (NTS)
SQLNET.AUTHENTICATION_SERVICES = (NONE)
Check Path at Env Var
Listener rights issue
Restart Listener
Standby Database not automatically startup issue
What is the value of REMOTE_LOGIN_PASSWORDFILE parameter?
Please change the owner of the Oracle process
Start->Settings->Control Panel->Services
Locate and highlight the "OracleServiceSID"
Click on the "Startup" button
In the "Log On As", choose "This Account"
Use the "..." button to browse to the "OracleAdmin" or Administrator user
Choose in "List Names From" your host
Provide the password of this user and confirm it
Repeat for the "OracleStartSID", "OracleTNSListener" and any
other Oracleservice you are using.
Be sure that the service startup is "Automatic"
ORA_<SID>_AUTOSTART =
ORA_<SID>_PFILE =
ORA_<SID>_SHUTDOWN =
ORA_<SID>_SHUTDOWNTYPE =
ORA_<SID>_SHUTDOWN_TIMEOUT =
Research:
=========
WIN: Automatic Startup of the Database when Using O/S Authentication ( Note 116979.1 )
How to configure Database Control to Start Automatically on Server Reboot / Shutdown Note 1282530.1
Windows Service Not Starting Automatically At Server reboot ( Doc ID 1264404.1 )
LD Login Error Table Definitions have undergone a change
select table_name from dba_tables where owner='LDBO' and temporary = 'Y' and table_name='TBLTEMPOPERATIONSTATISTICS';
DRop TABLE "LDBO"."TBLTEMPOPERATIONSTATISTICS" ;
CREATE GLOBAL TEMPORARY TABLE "LDBO"."TBLTEMPOPERATIONSTATISTICS"
( "NOPERCODE" NUMBER(3,0),
"NSUBCODE" NUMBER(3,0),
"COPERATIONNAME" VARCHAR2(100 BYTE),
"CSTARTTIME" DATE,
"CENDTIME" DATE,
"NTOTALROWS" NUMBER(12,0),
"NINITIALROWS" NUMBER(12,0),
"NFETCHROWS" NUMBER(12,0)
) ON COMMIT PRESERVE ROWS ;
ORA-00322 ORA-00312
ORA-00322 ORA-00312
Errors in file D:\APP\ADMINISTRATOR\diag\rdbms\rakshak\rakshak\trace\rakshak_ora_10232.trc:
ORA-00322: log 3 of thread 1 is not current copy
ORA-00312: online log 3 thread 1: 'E:\RKDATABASE\REDO03.LOG'
recover database using backup controlfile;
E:\RKDATABASE\REDO03.LOG
ALTER DATABASE OPEN RESETLOGS;
Errors in file D:\APP\ADMINISTRATOR\diag\rdbms\rakshak\rakshak\trace\rakshak_ora_10232.trc:
ORA-00322: log 3 of thread 1 is not current copy
ORA-00312: online log 3 thread 1: 'E:\RKDATABASE\REDO03.LOG'
recover database using backup controlfile;
E:\RKDATABASE\REDO03.LOG
ALTER DATABASE OPEN RESETLOGS;
EXPDP Privileges ORA-31631 ORA-39161
create user expdpuser identified by expdpuser default tablespace usr temporary tablespace temporary;
grant connect, resource, exp_full_database,IMP_FULL_DATABASE to expdpuser;
grant all on directory to expdpuser;
grant connect, resource, exp_full_database to ldbo;
ORA-00980: synonym translation is no longer valid
select * from dba_synonyms s
where table_owner not in('SYSTEM','SYS')
and db_link is null
and not exists
(select 1
from dba_objects o
where s.table_owner=o.owner
and s.table_name=o.object_name);
ORA-01172 ORA-01151
ORA-01172: recovery of thread 1 stuck at block 45 of file 2
ORA-01151: use media recovery to recover block, restore backup if needed
shut immediate
startup mount
recover database;
alter database open;
ORA-01151: use media recovery to recover block, restore backup if needed
shut immediate
startup mount
recover database;
alter database open;
Subscribe to:
Posts (Atom)