If you happen to be using the same platform (cpu/OS) it is fairly simple to get this up and running, if you know from which version of Oracle this backup is AND the backup is taken in the correct way. In your case, since all you have is ctl and dbf files, it should have been a COLD backup.
If all of the above is not in place: forget it.
If all of the above is in place:
- create a init.ora file containing the dbname, db_unique_name, and control_files parameter. The latter one points to at least one of your ctl files. With a little luck you can guess the dbname from the file names.
- install the correct oracle rdbms version in a location called ORACLE_HOME
- export ORACLE_HOME=/where/your/Oracle/product/version/home_1 is
- export PATH=$ORACLE_HOME/bin:$PATH
- sqlplus / as sysdba
- startup nomount pfile=your_full_name_of_init.ora from step 1
- alter database mount - this accessed the ctl files and checks dbname. Fix dbname in init.ora if reported wrong and shutdown abort the instance to start over at step 5.
- now you are able to look into the original files locations. If your files are in exactly the same locations as the original database thi sis easy: alter database open read only;
If any error: hire a dba to help you. If step-8 gives problems because of incorrect file locations: you can rename the files one by one, or create a text dump of the controlfile, edit that dump for the correct locations and use it to create a new controlfile.
Oracle is very flexible and many situations can be handled.
In your case, your database is 18.104.22.168 on Windows. You could try to request a download from oracle support and perform an upgrade. This is the easiest is your dbf locations are the same as on the original system (they are in the controlfile)