su -
# groupadd dba
# useradd -g dba oracle

kernel.shmall = 2097152
kernel.shmmax = 2147483648
kernel.shmmni = 4096
kernel.sem = 250 32000 100 128
fs.file-max = 65536
net.ipv4.ip_local_port_range = 1024 65000
net.core.rmem_default = 262144
net.core.rmem_max = 262144
net.core.wmem_default = 262144
net.core.wmem_max = 262144

session required /lib/security/pam_limits.so

session required pam_limits.so

oracle    soft  nproc  2047
oracle    hard  nproc  16384
oracle    soft  nofile  1024
oracle    hard  nofile  65536

# mkdir /opt/oracle
# mkdir /opt/oracle/102
# chown -R oracle:dba /opt/oracle

ORACLE_BASE=/opt/oracle
ORACLE_HOME=$ORACLE_BASE/102
ORACLE_SID=ORCL
LD_LIBRARY_PATH=$ORACLE_HOME/lib
PATH=$PATH:$ORACLE_HOME/bin

export ORACLE_BASE ORACLE_HOME ORACLE_SID LD_LIBRARY_PATH PATH

ORACLE_BASE=/opt/oracle
ORACLE_HOME=$ORACLE_BASE/102
ORACLE_SID=ORCL
LD_LIBRARY_PATH=$ORACLE_HOME/lib:$ORACLE_HOME/lib32
PATH=$PATH:$ORACLE_HOME/bin

export ORACLE_BASE ORACLE_HOME ORACLE_SID LD_LIBRARY_PATH PATH

cd /home/oracle
. .bash_profile

rpm -q binutils gcc glibc glibc-headers glibc-kernheaders glibc-devel compat-libstdc++ cpp compat-gcc make compat-db compat-gcc-c++ compat-libstdc++ compat-libstdc++-devel setarch sysstat pdksh libaio libaio-devel --qf '%{name}.%{arch}\n'|sort

rpm -q binutils compat-db compat-libstdc++-33 glibc glibc-devel glibc-headers gcc gcc-c++ libstdc++ cpp make libaio ksh elfutils-libelf sysstat libaio libaio-devel setarch --qf '%{name}.%{arch}\n'|sort

binutils.i386
compat-gcc-7.3-2.96.128.i386
compat-gcc-c++-7.3-2.96.128.i386
compat-libstdc++-7.3-2.96.128.i386
compat-libstdc++-devel-7.3-2.96.128.i386
cpp.i386
gcc.i386
gcc-c++.i386
glibc.i386
glibc-common.i386
glibc-devel.i386
glibc-headers.i386
glibc-kernheaders.i386
libstdc++.i386
libstdc++-devel.i386
libaio
libai-devel.i386
pdksh.i386
setarch.i386
sysstat.i386

binutils.x86_64
compat-db.x86_64
compat-libstdc++-33.i386
compat-libstdc++-33.x86_64
cpp.x86_64
elfutils-libelf.i386
elfutils-libelf.x86_64
gcc-c++.x86_64
gcc.x86_64
glibc-devel.i386
glibc-devel.x86_64
glibc-headers.x86_64
glibc.i686
glibc.x86_64
ksh.x86_64
libaio-devel.i386
libaio-devel.x86_64
libaio.i386
libaio.i386
libaio.x86_64
libaio.x86_64
libstdc++.i386
libstdc++.x86_64
make.x86_64
setarch.x86_64
sysstat.x86_64

# rpm -ivh libaio-0.3.96-3.src.rpm
# cd /usr/src/redhat/SPECS/
# rpmbuild -bb --target i386 libaio.spec
# cd ../RPMS/i386/

# rpm -ivh <package_name>.rpm

unzip 10201_database_linux32.zip

gunzip 10201_database_linux_x86_64.cpio.gz
cpio -idmv <10201_database_linux_x86_64.cpio

[Certified Versions]
Linux=redhat-3,SuSE-9,redhat-4,UnitedLinux-1.0,asianux-1,asianux-2,redhat-5

cd db/Disk1/
./runInstaller

ORCL:/opt/oracle/102:Y

#!/bin/bash
#
# oracle Init file for starting and stopping
# Oracle Database. Script is valid for 10g and 11g versions.
#
# chkconfig: 35 80 30
# description: Oracle Database startup script

# Source function library.

. /etc/rc.d/init.d/functions

ORACLE_OWNER="oracle"
ORACLE_HOME="/opt/oracle/102"

case "$1" in
start)
echo -n $"Starting Oracle DB:"
su - $ORACLE_OWNER -c "$ORACLE_HOME/bin/dbstart $ORACLE_HOME"
echo "OK"
;;
stop)
echo -n $"Stopping Oracle DB:"
su - $ORACLE_OWNER -c "$ORACLE_HOME/bin/dbshut $ORACLE_HOME"
echo "OK"
;;
*)
echo $"Usage: $0 {start|stop}"
esac

chmod 750 /etc/init.d/oracle
chkconfig --add oracle --level 0356

113094m Bios Bin Full [best] -

The 113094m BIOS BIN file is a critical firmware component primarily used for motherboard repair, data recovery, and hardware troubleshooting. Unlike standard executable BIOS updates, a .bin file is a raw binary image of the BIOS chip's contents, typically required when using an external hardware programmer to "unbrick" a dead motherboard. What is the 113094m BIOS BIN Full File?

The term "113094m" refers to a specific BIOS version or motherboard identifier. A "full" BIN file means it contains the complete data structure of the BIOS, including:

Main BIOS Region: The core code that initializes hardware and boots the OS.

ME (Management Engine) Region: Security and management features for Intel-based systems.

Descriptor Region: Defines the layout and access permissions for different parts of the flash memory. Why You Might Need This File

Standard updates often only overwrite the "main" region. You need the full .bin file in these scenarios: 113094m bios bin full

Corrupted BIOS: If the system won't POST (Power-On Self-Test) due to a failed update.

External Programming: When using tools like the CH341A Programmer to flash the chip directly.

Password Removal: Some repair technicians use full dumps to reset hardware-level passwords.

Hardware Swaps: If the BIOS chip itself is physically damaged and needs replacement. How to Use a .bin BIOS File

Flashing a .bin file is more complex than a standard update and usually follows these steps: The 113094m BIOS BIN file is a critical

Extraction: If you only have an .exe file from a manufacturer like HP or Dell, you may need to use 7-Zip to extract the raw .bin file from the installer.

Backup: Before writing the new file, always use your programmer to Read and Save the current contents of the chip as a backup.

Flashing: The programmer software (e.g., Asus EZ Flash for internal methods or specialized software for external programmers) will "Erase" the chip first and then "Write" the new 113094m file. Warning on Hardware Risks

Flashing a BIOS with the wrong .bin file can permanently disable your motherboard. Ensure the file matches your specific motherboard revision and part number exactly before proceeding. Extract Bios BIN file from EXE file

---

What is the 113094m BIOS?

The string "113094m" typically refers to a specific version label found within the firmware header or the filename provided by the manufacturer or a dump repository. In the context of board repair, this isn't just a random number; it signifies the exact instruction set intended for the embedded controller (EC) and the main system BIOS. What is the 113094m BIOS

Most technicians encounter this string when working on laptops where the main BIOS and EC firmware are tightly coupled. If you are looking for a "full" BIOS BIN file, you aren't just looking for an update patch. You are looking for a complete dump that includes:

1. The Main BIOS: The system firmware (UEFI/BIOS).
2. The EC (Embedded Controller) Firmware: Controls power management, keyboard, and fans.
3. The Descriptor Region: Critical configuration data for the SPI flash.

A mismatch between the BIOS version and the EC version (e.g., flashing a main BIOS that doesn't match the EC version currently on the board) can result in a laptop that turns on but produces no image or immediate shutdowns.

What is a .bin File?

Before we dive into the numbers, let’s look at the container. A .bin file (short for binary) is a raw data dump. In the context of a BIOS (Basic Input/Output System) or UEFI, this file is the literal DNA of the motherboard. It contains the code that wakes the computer from its coma, initializes the hardware, and hands control over to the operating system.

The keyword "full" in the filename is crucial. It implies this isn't just a partial update patch. It is a complete, standalone image of the chip's memory—essential for recovering a "bricked" system that won't even attempt to boot.

Fix 1: Verify the BIOS File Size and Chip Capacity

First, check your hardware’s specifications:

1. Identify your BIOS chip physically: Locate the 8-pin SOIC or WSON chip on the motherboard. Common part numbers include:
   • W25Q64 = 8 MB (64 Megabits)
   • W25Q128 = 16 MB (128 Megabits)
   • W25Q256 = 32 MB (256 Megabits)
2. Check your .bin file size: Right-click the file > Properties. Size in bytes.
   • 8,388,608 bytes = 8 MB chip
   • 16,777,216 bytes = 16 MB chip
3. If the file is larger than the chip: You have the wrong BIOS. Download the correct version for your exact motherboard revision (e.g., Rev 1.0 vs Rev 2.0).

Fix 2: Correct the Chip Model in Your Programmer Software

If the file size matches the chip’s physical capacity but the error persists, the software may be misreading the chip.

• In CH341A Programmer / NeoProgrammer:
  • Go to the chip selection menu.
  • Do NOT use "Auto Detect". Manually select the exact chip model from the list (e.g., Winbond W25Q128FVSG).
  • Re-attempt the write operation.
• In flashrom (Linux/Command line):
  • Force the chip model: flashrom -p ch341a_spi -c "W25Q128.V" -w bios.bin

chmod 750 /etc/init.d/oraemctl
chkconfig --add oraemctl --level 0356

su -
# rpm -ivh rlwrap*.rpm
# exit
echo "alias sqlplus='rlwrap sqlplus'" >> /home/oracle/.bash_profile
echo "alias adrci='rlwrap rman'" >> /home/oracle/.bash_profile
. /home/oracle/.bash_profile