File Name from Folder Path

How do you retrive the file name from the folder Name from Folder path:

flname := 'C:\Folder1\SubFolder1\SubFolder3\MyTest.xls';

SELECT substr(flname, instr(flname, '\', -1) + 1) FROM dual;

Output will be
MyTest.xls

SQL Loader

All you need is CTL file, data file and the table to put in the data

Control File (Test.ctl)

LOAD DATA

TRUNCATE

INTO TABLE EMP

FIELDS TERMINATED BY "," OPTIONALLY ENCLOSED BY '"' TRAILING NULLCOLS

(

emp_id "trim(:emp_id)",

emp_name "trim(:emp_name)",

emp_dept "trim(:emp_dept)"

)

Data file would be (Test.csv)

emp_id,emp_name,emp_dept

1,John,10

2,Jane,30

Go to the command Prompt and type

C:\ >sqlldr.exe userid=scott/tiger@oradb control=c:\sqldrtest\TEST.ctl log= c:\sqldrtest\20110922.LOG bad= c:\sqldrtest\20110922.BAD data= c:\sqldrtest\Test.csv errors=1000

SQL*Loader: Release 10.2.0.4.0 - Production on Thu Sep 22 11:08:02 2011

Copyright (c) 1982, 2007, Oracle.  All rights reserved.

Commit point reached - logical record count 2

It is always a good practice to have Errors=0, so that the file does not get processed even if there is one error

"Failed to access IIS metabase" Error

I was working on a sample web project, where in I came across this error "Failed to access IIS metabase". This happened only when I tried to run the web project by "Using Local IIS Web Server" instead of the default "Use Visual Studio Development Server".  From the Error I was able to find out it is something related to IIS web server only. When I tried to dig into this issue, I understood this is because of my IIS installation. I installed IIS web server after installing my ASP.NET framework.

I got few suggestions to fix this error first one was 
 "To repair framework from the Add/Remove programs" : But for some reasons this did not work

Next suggestion was
  "To Register ASP.NET on IIS" . 
Registering ASP.NET on IIS is not just a matter of associating the various .aspx, .asmx, .axd, .ashx and the other ASP.NET extensions to the aspnet_isapi.dll ISAPI, more has to be done to create the ASP.NET account and to set it for ASP.NET requests, register the ISAPI itself and other stuff.

To do this we will have to use the aspnet_regiis utility
1. Click Start -> run -> cmd - ENTER
2. At the command prompt, type the following, and then press ENTER:
"%windir%\Microsoft.NET\Framework\<version>\aspnet_regiis.exe" -i
   Here version is the version number of the .NET Framework that are installed on our server
   -i is the register the .NET Framework 
   -u is to unregister the .NET Framework

We will have to do this for all the versions installed on the server. I did the following

"%windir%\Microsoft.NET\Framework\v1.1.4322\aspnet_regiis.exe" -i
"%windir%\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe" -i
"%windir%\Microsoft.NET\Framework\v4.0.30319\aspnet_regiis.exe" -i

My IIS web server started working!!!

How do you test Microsoft Visual Studio .NET Installation

1. Take a Sample aspx file, Let us say "test.aspx" And copy that to "c:\Inetpub\wwwroot" folder
2. Now open browser and type http://localhost/test.aspx: You should be able to see the page if your Microsoft Visual Studio .NET installation is right. aspx programs need the .NET framework to run. The .NET framework is one of the Windows component updated by the Microsoft Visual Studio .NET installation

How do you test IIS Installation

1. Take a Sample HTML file, Let us say "test.html" And copy that to "c:\Inetpub\wwwroot" folder
2. Now open browser and type http://localhost/test.html: You should be able to see the page if your IIS installation is right

MMC could not create the Snap-In -IIS

If you get the following error while opening IIS,

MMC could not create the Snap-In

From the Command Line run, to resolve the issue

“regsvr32 %windir%\system32\inetsrv\inetmgr.dll”

This command line basically registers the IIS Server DLL

Signature has been changed Error

ORA-04062 (Signature has been changed)

This error is cause when you have a master Schema & local schema, And the package Spec is not in sync with both the schema.

Solution:

  Compile the package one more time in both the schema.