Ok, I tried it out of desperation myself. I deleted the sqlnet.ora files and manually re-created them with the proper entry and that fixed the problem I had used the cat command to write to them previously. I have no idea what was wrong with them previously. On Sat, Aug 11, 2012 at 8:31 PM, Andrew Kerber <andrew.kerber@xxxxxxxxx>wrote: > I have found that it is very picky on the sqlnet.ora file in the database > homes. Once I had to copy in a sqlnet.ora that I thought was identical to > the one that was already there, and that fixed the problem. Yeah, I was > desperate at that time. > > On Sat, Aug 11, 2012 at 5:37 PM, John Smith <john40855@xxxxxxxxx> wrote: > >> Well, I thought I followed all the steps for putting in the patch for the >> listener poison bug. But when I reach the point where its time to switch >> the remote listener to the secure port, I cant get the instances to >> register on the secure port. They show up when I switch it back to the >> unsecure port. So I assume its something to do with my wallet settings. >> I >> added the secure port for the scan listener, and restarted. I restarted >> the instances after I changed the sqlnet.ora to use a wallet for the db >> instances. >> I have the same wallet location in the sqlnet.ora for the databases, and >> the listener and sqlnet.ora for the asm instance (this is 11.2.0.2). Can >> anyone point me to some instructions on how to figure out why the listener >> wont register. Is there a log file or anything I can look at? >> >> >> -- >> //www.freelists.org/webpage/oracle-l >> >> >> > > > -- > Andrew W. Kerber > > 'If at first you dont succeed, dont take up skydiving.' > -- //www.freelists.org/webpage/oracle-l