Can’t umount Red-Hat filesystem with error “This utility only unmounts cifs filesystems” either with force?
[@Linux-redhat5 ~]$ cat /etc/redhat-release Red Hat Enterprise Linux Server release 5.11 (Tikanga)
ERROR:
[@Linux-redhat5 /]# umount /cifsfilesystem/data/custom This utility only unmounts cifs filesystems. This utility only unmounts cifs filesystems. This utility only unmounts cifs filesystems.
Hey!
Strange question, right? You should know you applications and databases and how everything works, right?
Happen that some days ago a client requested me to identify from which database is a service_name. Easy? Not if the server have 46 database instances running…
Ok, now how can I can this information as quick as possible?
I know that the command below give me all distinct databases in CRS:
/u01/app/12.1.0.2/grid/bin/crsctl stat res -t -w "TYPE = ora.database.type"
Now, lets make some sed magic:
[root@nprd01dbadm01 ~]# /u01/app/12.1.0.2/grid/bin/crsctl stat res -t -w "TYPE = ora.database.type" |grep ora. |sed 's/ora./srvctl status service -d /' |sed 's/.db/ |grep \$1/' | head -1 srvctl status service -d dba |grep $1
More“Shellscript: Which database is this service_name from?”
To connection between unix machine with teradata environment is needed to install ODBC Driver and some others components (dependencies). All Items can be found in Teradata Downloads site: https://downloads.teradata.com/
Teradata OBDC Driver has 3 dependecies:
1. Shared common components for Internationalization (TDICU)
2. Teradata GSS client package (TeraGSS)
3. Teradata Tools and Utilities Base (TTU)
After download all items, run as root: rpm -ivh “component_name” –nodeps
Eg: rpm -ivh teragss1510-15.10.02.06-1.noarch.rpm --nodeps
Use “–nodeps” only to not need to install in order
Would you to clone some GoldenGate home, but you have too many extract / pump / replicats?
It will take an eternal day?
Try to use this script:
Hello everyone!
I already wrote a post about it but I think I was not clear and easy to find enough. So let me make another post about and add some information…
Ok, are you facing a “java.sql.SQLException: ORA-28040: No matching authentication protocol” after upgrade your database to 12c?
It’s related to old jdbc driver version in your application. Please review matrix available in this post and check your application. The MOS noted below have good information about it…
Hello!
After discover your new 12c targets you are facing target status down for MGMT targets, similar to image below?
And checking on server all looks to be ok, right?
Hello!
Have you ever killed a session in database and the session doesn’t disappear? Or yet, you killed the SPID of the session in OS and the session still running in database, but now you cannot see the SPID?
Very weird, but it happens. First of all, let us point some interesting items:
